"Marc Brett" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Nothing to do with NTP minutiae, and more to do with the imperfect US
> implementation of the new daylight saving time rules. Still of interest
> to
> chime-heads, methinks.
>
> http://www.passablynews.com/index.php?suba
Jason,
I recall that Paul Vixie was the author of that much-mangled driver. He
intended to support a number of TrueTime devices, including the GOES and
WWVB clocks which are no longer manufactured. The code has little
wiggles designed to support most if not all historic TrueTime devices
with o
Harlan Stenn wrote:
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Nigel Henry) writes:
>
> Nigel> [EMAIL PROTECTED] djmons]$ /usr/sbin/ntpq
> ntpq> pe
> Nigel> localhost.localdomain: timed out, nothing received ***Request timed
> Nigel> out
>
> This looks like ntpd is not running at the
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> We have a machine which is running NTP version 4 and it's in sync with
> its time server (a '*' appears in the output of ntpq -p; as we know
> the server marked * is the one which is chosen for synchronization).
A combination of those wit
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Hal Murray) wrote:
> I see the following when ntpd gets started before eth0 has made contact
> with dhcp. ntp.conf has a single server 192.168.1.3 that's on the
Your init.d scripts should not go beyond the DHCP query until you have
a valid IP a
On Wednesday 18 April 2007 03:06, Harlan Stenn wrote:
> Nigel,
>
> When you see 2 ntpd processes like that it means ntpd is still doing DNS
> resolution.
>
> H
Ok I've given up on the ntp-4.2.0.7 version on FC2, removed it , and built
from the tarball version 4.2.4p0. This version works ok on FC6
>The fail is final - thus you don't see any configured peers/servers.
>The reason is that ntpd cannot determine the interface it needs to
>send to that adress. that is usually caused by the network not
>being fully functional at the time when ntpd starts.
>
>You can:
> - delay ntpd start until th
[EMAIL PROTECTED] (Hal Murray) writes:
>>It should no longer be necessary to do this. NTP 4.2.4 support dynamic
>>IP addresses of the host and it will find and rebind the receiving
>>addresses automatically.
>
> I see the following when ntpd gets started before eth0 has made contact
> with dhcp.
>>> In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes:
kaleem> Hello, We have a machine which is running NTP version 4 and it's in
kaleem> sync with its time server (a '*' appears in the output of ntpq -p;
kaleem> as we know the server marked * is the one which is chosen for
kaleem> synchro
Nothing to do with NTP minutiae, and more to do with the imperfect US
implementation of the new daylight saving time rules. Still of interest to
chime-heads, methinks.
http://www.passablynews.com/index.php?subaction=showfull&id=1175830780
Better technical analysis here:
http://www.pittsburghliv
Does anyone have any insight into how Network Time Protocol works with the
Vehicle Modem Monitor (VMM wmc6300)?
I've been having some issue in changing the computer clock. I'm wondering
if this issue has to do with the tablet I'm using or is it the NTP within
the VMM.
ELB
___
Hello,
We have a machine which is running NTP version 4 and it's in sync with
its time server (a '*' appears in the output of ntpq -p; as we know
the server marked * is the one which is chosen for synchronization).
Now the problem
is that even if the machine is synchronizing with its time server a
>It should no longer be necessary to do this. NTP 4.2.4 support dynamic
>IP addresses of the host and it will find and rebind the receiving
>addresses automatically.
I see the following when ntpd gets started before eth0 has made contact
with dhcp. ntp.conf has a single server 192.168.1.3 that's
13 matches
Mail list logo
