Putting kerberos/ldap logs somewhere useful

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@lists.postgresql.org
Date: 2019-08-05T23:26:45Z
Lists: pgsql-hackers

Attachments

I got frustrated just now because this:

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2019-08-05%2021%3A18%3A23

is essentially undebuggable, thanks to the buildfarm's failure to
capture any error output from slapd.  That's not the buildfarm
script's fault: it's willing to capture everything placed in the
agreed-on log directory.  But the TAP test script randomly places
the daemon's log file somewhere else, one level up.  The kerberos
test script has the same problem.

Hence, I propose the attached.  This just moves the actual log
files ... we could possibly move the daemons' .conf files as well,
but I think they're probably not variable enough to be interesting.

			regards, tom lane

Commits

  1. Save Kerberos and LDAP daemon logs where the buildfarm can find them.