On Sun, 25 Jun 2006, Brian A. Seklecki wrote: >> you do a "reload" command or whenever there is a sudden clock shift, which > > Do you postulate that large clock shifts on NTP synchronized systems are > an indication of a low-level hardware problem?
It is common for initial NTP or rdate set failures (usually caused by conection refused on the server) to result in the date being set to 2039 or 1970. It's an ancient and well known bug in the client software which has never been fixed The time usually needs to be corrected manually after this happens. A lot of programs react badly to utime jumping backwards, not just Bacula. Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
