Re: "runtime went backwards" message in logs
- From: "Julian H. Stacey" <jhs@xxxxxxxxxxxxxxxx>
- Date: Fri, 30 Dec 2005 01:39:55 +0100
> PS. Not sure if this have anything to do with it (the message mentions CPU
> time, not the clock), but I'm running a ntp daemon, to synchronize time...
Highly likely it has a Lot to do with it :-) Maybe the master time
server had `date` run manually, or otherwise shifted, or came back
on net after an outage, & the systems noticed drifted time & corrected etc.
man ntpd
man ntp.conf
etc :-)
--
Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com
Mail in Ascii, HTML=spam. Ihr Rauch = meine allergischen Kopfschmerzen.
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: "runtime went backwards" message in logs
- From: Koen Martens
- Re: "runtime went backwards" message in logs
- From: Derek Kuliński
- Re: "runtime went backwards" message in logs
- References:
- "runtime went backwards" message in logs
- From: Derek Kuliński
- "runtime went backwards" message in logs
- Prev by Date: "runtime went backwards" message in logs
- Next by Date: Re: "runtime went backwards" message in logs
- Previous by thread: "runtime went backwards" message in logs
- Next by thread: Re: "runtime went backwards" message in logs
- Index(es):
Relevant Pages
|
|