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]
freq
I see those messages too, but the time stays accurate.
-Original Message-
From: Christopher Chan [mailto:christopher.c...@bradbury.edu.hk]
Sent: Saturday, July 09, 2011 9:07 AM
To: openindiana-discuss@openindiana.org
Subject: [OpenIndiana-discuss] ntpd not keeping time in sync
Hi all,
On Saturday, July 09, 2011 10:30 PM, Dan Swartzendruber wrote:
I see those messages too, but the time stays accurate.
Okay, so maybe flaky electricity does not affect ntpd...but would it
mess up the system clock?
-Original Message-
From: Christopher Chan [mailto:christopher.c...@
-Original Message-
From: Christopher Chan [mailto:christopher.c...@bradbury.edu.hk]
Sent: Saturday, July 09, 2011 10:53 AM
To: openindiana-discuss@openindiana.org
Subject: Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On Saturday, July 09, 2011 10:30 PM, Dan Swartzendruber wro
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:
Hmmm, good question!
-Original Message-
From: Gary Gendel [mailto:g...@genashor.com]
Sent: Saturday, July 09, 2011 11:49 AM
To: openindiana-discuss@openindiana.org
Subject: Re: [OpenIndiana-discuss] ntpd not keeping time in sync
Christopher,
A silly question... Is this on a dual-boot s
On Jul 9, 2011, at 8:48 AM, Gary Gendel wrote:
> I suppose this could be true of a virtual machine resetting the time as well.
A guest OS should never be allowed to adjust its hosts clock. Sometimes a
failing motherboard battery can cause issues but NTP should be correcting them.
Have you tried
No, I think he meant resetting the time in the BIOS of the VM.
-Original Message-
From: Gary Driggs [mailto:gdri...@gmail.com]
Sent: Saturday, July 09, 2011 1:42 PM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] ntpd not keeping time in sync
On Jul 9, 2011, at 8:
> Nikola M wrote:
> > I would like to propose shorter subjects in the mailing lists.
> > (Caiman-team,G11n-team,Jds-team,Sfw-team, rest are Ok I think)
> PLEASE
> Consider shortening Subject lines for Mailing list subjects.
> PLEASE.
Most of us use GUI-based email readers that handle >80char subje
It wouldn't be an LSI 3801/3081 board by any chance? I've seen some rather bad
issues like this with those boards
roy
- Original Message -
> Indeed, right now zpool status -v is reporting only 1 unrecoverable
> error.
> However, other LUNs aren't recognized by VMWare as VMFS volumes
> an
>On 10/07/2011 5:43 a.m., Dan Swartzendruber wrote:
No, I think he meant resetting the time in the BIOS of the VM.
-Original Message-
From: Gary Driggs [mailto:gdri...@gmail.com]
Sent: Saturday, July 09, 2011 1:42 PM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss
AFAIK, at least historically, the hardware battery clock time is expected
(without some tweaks, to the extent that a given version allowed those) by
Windows to be in local time. Operating systems that keep their internal time
in something else (.e.g. Unix and related, where it's supposed to be
-Original Message-
From: Mark [mailto:mark0...@gmail.com]
Sent: Saturday, July 09, 2011 4:51 PM
To: openindiana-discuss@openindiana.org
Subject: Re: [OpenIndiana-discuss] ntpd not keeping time in sync
>On 10/07/2011 5:43 a.m., Dan Swartzendruber wrote:
>
> No, I think he meant resetti
On 10/07/2011 8:54 a.m., Richard L. Hamilton wrote:
AFAIK, at least historically, the hardware battery clock time is expected
(without some tweaks, to the extent that a given version allowed those) by
Windows to be in local time. Operating systems that keep their internal time
in something el
/listinfo/openindiana-discuss
>>
The hardware RTC is only read at boot and sets the initial date/time.
The OS will adjust it's internal time from this initial reference and
it's timezone, hence different times between cmos rtc and server e.g
daylight time.
Then the hardware time ticks are coun
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
On Sunday, July 10, 2011 09:00 AM, Christopher Chan wrote:
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 r
17 matches
Mail list logo
