Thank you for teaching me that. I was wrong in my cause of the problem. My mistake was to use this line in bacula-fd.conf
FDAddress = d420.local #FDAddress = 127.0.0.1 I suppose avahi or whatever helps .local work is not ready when the script runs. On Fri, 2008-06-20 at 04:46 +0000, Ante Karamatić wrote: > Errr... Ubuntu uses upstart so, INIT INFO shouldn't have any effect: > > $ ps ax | grep bacula > xxxx pts�0 S+ 0:00 grep bacula > $ sudo �etc�init.d�bacula-fd start > * Starting Bacula File daemon... [ OK > ] > $ ps ax | grep bacula > xxxx ? Ssl 0:00 �usr�sbin�bacula-fd -c �etc�bacula�bacula-fd.conf > xxxx pts�0 R+ 0:00 grep bacula > $ > > ** Changed in: bacula (Ubuntu) > Importance: Undecided => Medium > Status: New => Triaged > -- Tim Richardson, CPA [EMAIL PROTECTED] +61 458 998 541 GMT+10 all contact details: http:��www.tim-richardson.net�contact Using Linux. -- bacula-fd does not start when installed via bacula-client https://bugs.launchpad.net/bugs/241480 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
