Um 05:11 Uhr am 01.07.06 schrieb John Goerzen:
On Thu, Jun 29, 2006 at 05:36:41PM +0200, Kern Sibbald wrote:
I don't consider this an upstream bug, but rather a problem of
administration
of database access to be resolved at installation time.
The Debian bacula packages will help you set
On Sat, Jul 01, 2006 at 01:50:00PM +0200, Sven Hartge wrote:
Um 05:11 Uhr am 01.07.06 schrieb John Goerzen:
password for use with MD5 on install time as well.
I see two problems here:
a) debconf allows the user to use ident sameuser, but this cannot work
without manually changing
Um 08:33 Uhr am 01.07.06 schrieb John Goerzen:
b) ident sameuser is the only method configured for local type
connections using the unix socket of postgres. While _I_ am perfectly
able to reconfigure postgres to also require md5 when using the
socket, other users might
Hello,
This is indeed a problem, and not one that I consider an upstream bug. The
basic problem is that Bacula cecks if it can open the database prior to
becoming a daemon and thus prior to dropping root privilege. It is the only
way, it can properly print the message and exit.
When it
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,
5 matches
Mail list logo
