On Mon, Feb 21, 2005 at 02:07:18PM +0200, Nadav Har'El wrote: > On Mon, Feb 21, 2005, Tzafrir Cohen wrote about "system clock loops": > > The following is from the output of 'date' run from the same shell about > > 1 second apart: > > > > 12:13:37 > > 13:25:08 > > 12:13:34 > >... > > > > Obviously anything that assumes a steady system clock misbehaves. > > > > Any idea what else may play with the system clock? > > > > Kernel is 2.6.8-2-686 (14), the current Debian-sarge kernel. > > I have seen this sort of nonsense when using AFS or Kerberos, which try to > keep their own time, based on bad servers, and force their notion of time > on the computer.
Not here. The computer is an NFS server, though. After many tinkerrings I rebotted the computer to see if it could make the problem go away. It has. For about an hour or so. And again, when it goes to the "future" it seems to have the safe offset of ~ 71:31 (4291 seconds). > > If that's not your problem (and it most likely isn't), are there any > interesting lines in /var/log/messages? Also, what does "hwclock" return? nothing. All's well according to the logs :-( -- Tzafrir Cohen | New signature for new address and | VIM is http://tzafrir.org.il | new homepage | a Mutt's [EMAIL PROTECTED] | | best ICQ# 16849755 | Space reserved for other protocols | friend ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
