I just installed 1.36.2-1 and everything appears to have worked. Of course, I haven't done a backup yet... I had done an abortive earlier install, and then purged it. There remained a bacula user on the system, but not in postgres.
However, there were a number of questions in the setup that were unclear, and I'm not sure I answered them correctly. This note is to ask if my answers were OK, and to let you know about the areas that I, at least, found confusing. ---------------------------------------- Where is the PostgreSQL server? localhost ----------------------------------------- I have everything on one system (at least for now), so I'm probably safe. But I know bacula is designed to work in a multi-machine environment. Does the response to this question need to be something that will work from any host? ------------------------------------------- Please, enter the password which Bacula will use to connect to PostgreSQL. PostgreSQL password -------------------------------------------- This was disturbing because in my setup, which I think is the Debian default, authentication is checking that you are the Unix user of the same name as the bacula user (AFAIK). To do admin stuff, you su to postgres. So authentication is not by name/password. Further, if the postgres unix user has a password, I don't know it. So I just hit enter. Then I said ----------------------------------------------- PostgreSQL 'root' username postgres ----------------------------------------------- As I say, it seems to have worked. One other peculiarity I notice is that postgres, not bacula, is the owner of bacula database. There is a bacula user, and it appears to have all necessary privileges on the relevant tables (I just spot checked table file). I'd also like to thank Jamie ffolliott (spelling doesn't look right, but that's what your mail client said). Ross -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
