Package: bacula-sd Version: 5.2.5 The init script for bacula-sd, when invoked to stop the daemon, should check to see if bacula-sd has actually terminated before returning.
On a slow machine, or virtual machine, it can take upwards of half a second for bacula-sd to terminate, once sent the signal. Currently the init script returns immediately, which can result in tools such as puppet failing to start the daemon immediately after stopping it (after a configuration change, for example). Logic already exists in the bacula director init script to handle a similar scenario, I would suggest this is extended to the storage daemon (and file daemon if necessary). - Mike -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
