On Monday 26 June 2006 04:06, 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?
No. In principle there should be no large clock shifts from NTP except when
your machine is booting. If NTP does shift the clock more than 5 minutes (if
I remember the code correctly) this could trigger the problem, which is a
Bacula issue.
>
> Of course, ACPI / APM state changes could cause this, but... ?
Given the fact that putting a laptop to sleep seemed to trigger the problem
(i.e. Bacula noticed the clock shift and took corrective action but fell into
a bug) I would guess that sleeping laptops and clock shifts go together.
Large clock shifts (more than a few milliseconds) can always be "fatal" or
disruptive to user programs, especially programs such as Bacula that have
schedulers ...
With the patch Bacula *should* be more or less resistant to clock shifts.
--
Best regards,
Kern
(">
/\
V_V
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
