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 attempts to connect to the database the first time, Bacula will be running as root, but it will use the correct database name and the correct user id and password. If you have set the Bacula database to *require* that the user id specified corresponds to the Unix user id that is running, then you will need to configure the Bacula database to either accept root or bacula logins. Otherwise, a simpler method is to allow any user to log into the bacula database providing he has the userid and password for the database. This makes more sense because there are a lot of applications such as bacula-web that need to be able to read/write the Bacula database. I don't consider this an upstream bug, but rather a problem of administration of database access to be resolved at installation time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
