usually a service in bacula doesn't start at boot because it is running as the wrong user. While when you manually invoke it, it is running as the correct user. Make sure the scripts being used to start the director deamon have the correct permissions.
Jason David Hatcher wrote: > I run the Bacula (v2.0.1) server on a Fedora Core 5 machine named > "BACULA." When I boot this machine, only two of the three Bacula > daemons start. When I type "service bacula status," I see the > "bacula-dir daemon is stopped." > > [EMAIL PROTECTED] /]# service bacula status > bacula-sd (pid 1858) is running... > bacula-fd (pid 1871) is running... > bacula-dir is stopped > [EMAIL PROTECTED] /]# > > I can start the Bacula Director daemon manually by typing "service > bacula start." But how to I enable all three daemons to start upon > boot? > > Thanks, > David > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
