From: "Charles R. Tersteeg" <[EMAIL PROTECTED]>

> This is my server ntp.conf file:
>
> server  128.118.25.3
> server  128.105.201.11
> server  142.3.100.2

Only the first one of these seems to be running an ntp server accessible from
my location.

> #server 127.127.1.0     # local clock
> #fudge  127.127.1.0 stratum 10
>
> logfile /var/log/ntp.log # me added for sanity sake
>
> file /etc/ntp/drift
> multicastclient                 # listen on default 224.0.1.1

For what it is worth I do not use multicast.

> broadcastdelay  0.008
>
> authenticate no
> ---------------------------------------
> This is my client ntp.conf file:
>
> server  192.168.0.1 #ip of ntp server for network
>
> #server 127.127.1.0     # local clock
> #fudge  127.127.1.0 stratum 10
>
> logfile /var/log/ntp.log # me added for sanity sake
>
> file /etc/ntp/drift
> multicastclient                 # listen on default 224.0.1.1
> broadcastdelay  0.008
>
> authenticate no
> ------------------------------------
> If I specify the servers here, why do i need a step-tickers file in
> /etc/ntp with those same server names?

They are used before ntp starts to perform a coarse time correction
using ntpdate.

> I've tried both ways, i.e modifying the ntp.conf and adding a
> step-tickers, but the "clock" time stays the same and the internal cmos
> clocks are not updated either.  I do get this for output on "ntpq -p"

The below simply tells us that none of these machines is reachable as an
ntp server. Have you checked your firewall rules?

> server:
>      remote           refid      st t when poll reach   delay   offset
> jitter
> ==============================================================================
>  128.118.25.3    0.0.0.0         16 u    -   64    0    0.000    0.000
> 4000.00
>  128.105.201.11  0.0.0.0         16 u    -   64    0    0.000    0.000
> 4000.00
>  142.3.100.2     0.0.0.0         16 u    -   64    0    0.000    0.000
> 4000.00
>
> client:
>      remote           refid      st t when poll reach   delay   offset
> jitter
> ==============================================================================
>  192.168.0.1     0.0.0.0         16 u    -   64    0    0.000    0.000
> 4000.00
>
> I didn't add any cron job to update time by the hour or any other
> increment as noone said you had to that?  what am i missing here? or do
> i have it and my clocks don't know what time it is?

No, you don't set up a cron job. It is all taken care of in ntpd.

{^_^}



_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list

Reply via email to