Package: bacula-director-pgsql Version: 1.38.9-11 Severity: normal I just stumbled upon a little problem occuring with bacula and postgres.
The problem has already been outlined in http://article.gmane.org/gmane.comp.sysutils.backup.bacula.devel/4308 I verified the claims in this mail and, indeed, bacula-director tries to connect to the database as "root" and not as "bacula" which of course fails if postgres is configured with "ident sameuser", as it is in Debian. While this is an implementation error (and thus an upstream bug), Debian can work around this issue by changing the init script in the following way: --- bacula-director.ORIG 2006-06-19 12:44:29.000000000 +0200 +++ bacula-director 2006-06-19 12:42:59.000000000 +0200 @@ -10,7 +10,7 @@ NAME="bacula-dir" PORT=9101 DESC="Bacula Director" -ARGS="-c /etc/bacula/bacula-dir.conf -u bacula -g bacula" +ARGS="-c /etc/bacula/bacula-dir.conf" test -f $DAEMON || exit 0 @@ -51,7 +51,7 @@ # do_start() do_start() { - start-stop-daemon --start --quiet --pidfile $PIDFILE \ + start-stop-daemon --chuid bacula --start --quiet --pidfile $PIDFILE \ --exec $DAEMON -- $ARGS } This allows bacula to function in a correct and secure way as intended. Grüße, Sven.
