Negative and also negative for vm install.
This is the image on iron that I am talking about. I have not check the
time on the vbox guest though...
I have restarted ntpd too and set both broadcastclient and server
directives. Manually running ntpdate -u ${server} works and will
readjust time.
Christopher
On Saturday, July 09, 2011 11:48 PM, Gary Gendel wrote:
Christopher,
A silly question... Is this on a dual-boot system? I had a problem on
one machine where booting windows would change the bios clock so
bringing up OpenIndiana would be an hour off. I suppose this could be
true of a virtual machine resetting the time as well.
Gary
On 7/9/11 9:07 AM, Christopher Chan wrote:
Hi all,
Would flaky electricity cause the system clock to go 'haywire' and
ntpd to generate logs such as:
Jul 7 22:46:33 bradsuper1 ntpd[25341]: [ID 702911 daemon.notice]
frequency error 512 PPM exceeds tolerance 500 PPM
Jul 7 23:02:31 bradsuper1 ntpd[25341]: [ID 702911 daemon.notice]
frequency error 512 PPM exceeds tolerance 500 PPM
and lead to the system clock an hour behind after about 24 hours?
Christopher
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
