[ntp:questions] Re: "Can't set time of day: Interrupted system call" - who can help?
Harlan Stenn
stenn at whimsy.udel.edu
Tue Aug 19 08:25:05 UTC 2003
Martin Glora <glora at science-computing.de> writes:
> Aug 19 08:38:52 comp ntpd[28901]: ntpd 4.1.2 at 1.892 Tue Aug 19 08:07:54
> MEST 2003 (3)
> Aug 19 08:38:52 comp ntpd[28901]: precision = 10 usec
> Aug 19 08:38:52 comp ntpd[28901]: frequency initialized -500.000 from
> /usr/local/ntp/ntp.drift
This means that the last time ntpd was running it decided your machine's
internal clock was beyond ntpd's ability to correct.
> Aug 19 09:16:56 comp ntpd[28901]: Can't set time of day: Interrupted
> system call
> Aug 19 09:16:56 comp ntpd[28901]: time reset 0.520944 s
> Aug 19 09:16:56 comp ntpd[28901]: synchronisation lost
Wait an hour and see if the problem self-corrects at all.
Your system clock may simply keep time so badly that ntpd cannot correct
it.
This may be a hardware problem.
Are you running ntpd with the -N option (perhaps -N high)?
H
More information about the questions
mailing list