1. Is this reproducible? Yes, it is. 2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible. Well, this machine has been running Ubuntu and bacula for quite some time, so I can't be really sure that I'm not missing something.
I can tell you that I deinstalled bacula-director-mysql bacula-director- common bacula-fd bacula-sd bacula-sd-mysql and removed the init scripts. Dunno why these were not deinstalled. They are considered part of the configuration, and I did not use --purge. Then, I installed those packages again and rebooted. No bacula process was started, but I must admit that bacula-sd and bacula-fd had no chance of being started because the installation did not install the start scripts. Probably again because I did not use --purge when I removed the packages. I'm sorry that I don't have the time to experiment some more. And I don't want to lose my bacula configuration. -- Bacula daemons are not started during system boot https://bugs.launchpad.net/bugs/442125 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
