On 16 Sep 2005 at 11:42, Karl Cunningham wrote: > Some time ago this machine developed an occasional problem when started > where its hardware clock would come up with the wrong time. Rather than > replace the machine for such a trivial problem we put a line of code into > the initialization scripts that sets the system clock from our time server. > > This is what I think is happening: The OS's system clock is set to the bad > hardware value at boot, then the Bacula director starts and sets up jobs > that are scheduled to run in the next hour, then the startup script > corrects the system time to be right. As time advances the director will > start jobs at what it thought was the right time, but no longer is.
A possible solution: Make the Bacula script start after the time setting. How you do this varies from system to system. Under FreeBSD, I'd rename bacula.sh to z-bacula.sh (actually, that's its name anyway, so that Bacula starts up after MySQL/PostgreSQL). I'd also put the time correction to be early in the process, and you might also want to plug it directly into the Bacula start up script. Or better still, create a third script that first invokes the time correction script, then the Bacula startup script. -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/ ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
