On Thursday, July 14, 2011 04:38 PM, Mark wrote:
On 14/07/2011 11:54 a.m., Gary wrote:
On Wed, Jul 13, 2011 at 1:04 PM, Mark wrote:
The 500ppm ntp range limit is easy to exceed with virtual hardware,
since it
isn't "real time" orientated.
The original poster, Chris Chan, is running it on bar
On 14/07/2011 11:54 a.m., Gary wrote:
On Wed, Jul 13, 2011 at 1:04 PM, Mark wrote:
The 500ppm ntp range limit is easy to exceed with virtual hardware, since it
isn't "real time" orientated.
The original poster, Chris Chan, is running it on bare metal hardware.
Regardless, I've never had that
On Wed, Jul 13, 2011 at 1:04 PM, Mark wrote:
> The 500ppm ntp range limit is easy to exceed with virtual hardware, since it
> isn't "real time" orientated.
The original poster, Chris Chan, is running it on bare metal hardware.
Regardless, I've never had that issue with running NTP in guests
hoste
On 13/07/2011 8:37 p.m., Jonathan Adams wrote:
ntpdate once an hour/half hour in cron?, or grep for the message in a
loop and ntpdate if it sees the message?
That is a fix I have used for Virtual Linux guests, and it works well,
but don't run ntpd as well to avoid the port conflict.
The 500
ntpdate once an hour/half hour in cron?, or grep for the message in a
loop and ntpdate if it sees the message?
but that's just the hacker in me ...
On 13 July 2011 02:56, Christopher Chan
wrote:
> On Wednesday, July 13, 2011 09:54 AM, Christopher Chan wrote:
>>
>> On Wednesday, July 13, 2011 06:
On Wednesday, July 13, 2011 09:54 AM, Christopher Chan wrote:
On Wednesday, July 13, 2011 06:52 AM, Christopher Chan wrote:
On Wednesday, July 13, 2011 03:51 AM, Roy Sigurd Karlsbakk wrote:
Sigh...
ntpdate -u 192.168.9.1
10 Jul 09:01:15 ntpdate[29929]: step time server 192.168.9.1 offset
3317.
On Wednesday, July 13, 2011 06:52 AM, Christopher Chan wrote:
On Wednesday, July 13, 2011 03:51 AM, Roy Sigurd Karlsbakk wrote:
Sigh...
ntpdate -u 192.168.9.1
10 Jul 09:01:15 ntpdate[29929]: step time server 192.168.9.1 offset
3317.946738 sec
IIRC ntpd won't adjust the time if the difference
On Wednesday, July 13, 2011 09:13 AM, Gary Driggs wrote:
On Jul 12, 2011, at 3:52 PM, Christopher Chan wrote:
I have switched from broadcastclient to specifying 5 time servers. That seems
to have got it to behave properly.
That isn't a default setting in OI, is it? If so, I'd strongly advise
On Jul 12, 2011, at 3:52 PM, Christopher Chan wrote:
> I have switched from broadcastclient to specifying 5 time servers. That seems
> to have got it to behave properly.
That isn't a default setting in OI, is it? If so, I'd strongly advise against
it. In fact, I advise against using it at all s
On Wednesday, July 13, 2011 03:51 AM, Roy Sigurd Karlsbakk wrote:
Sigh...
ntpdate -u 192.168.9.1
10 Jul 09:01:15 ntpdate[29929]: step time server 192.168.9.1 offset
3317.946738 sec
IIRC ntpd won't adjust the time if the difference is too big, measured between
the system clock, inherited from
> Sigh...
>
> ntpdate -u 192.168.9.1
> 10 Jul 09:01:15 ntpdate[29929]: step time server 192.168.9.1 offset
> 3317.946738 sec
IIRC ntpd won't adjust the time if the difference is too big, measured between
the system clock, inherited from the hardware clock, and the ntp servers. I've
see this on
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
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
/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
011, at 1:43 PM, 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] ntpd not keeping ti
-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
ink 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
ana-discuss] ntpd not keeping time in sync
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
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
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
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
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:
-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
...@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,
Would flaky electricity cause the system clock to go 'haywire' and ntpd
to generate logs such as:
Jul 7 22:46:33 brads
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
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
26 matches
Mail list logo
