On Wed, 2003-12-24 at 00:20, sean darcy wrote:
> I'm trying to set up a gateway machine, which runs fc1, that will be a time
> server for a small mixed linux/windows network.
>
> I get:
>
> [root@gateway etc]# /usr/sbin/ntpq -p
> /usr/sbin/ntpq: read: Connection refused
>
> not surprising:
>
> [root@gateway etc]# ps -aux | grep ntp
> root 20150 0.0 0.5 4644 580 pts/0 S 16:23 0:00 grep ntp
>
> so I start it:
>
> [root@gateway etc]# /etc/rc.d/init.d/ntpd start
> ntpd: Synchronizing with time server: [ OK ]
> Starting ntpd: [ OK ]
>
> and /var/log/messages says it's up. Here's ALL the ntp stuff is messages:
>
> Dec 23 16:23:58 gateway ntpdate[20158]: step time server 66.187.224.4 offset
> 0.078712 sec
> Dec 23 16:23:58 gateway ntpd: succeeded
> Dec 23 16:23:58 gateway ntpd[20163]: ntpd 4.2.0@xxxxxxxx Tue Oct 28 05:43:36
> EST 2003 (1)
> Dec 23 16:23:58 gateway ntpd: ntpd startup succeeded
> Dec 23 16:23:58 gateway ntpd[20163]: precision = 2.000 usec
> Dec 23 16:23:58 gateway ntpd[20163]: no IPv6 interfaces found
> Dec 23 16:23:58 gateway ntpd[20163]: kernel time sync status 0040
>
>
> But, it's not:
>
> [root@gateway etc]# ps -aux | grep ntp
> root 20168 0.0 0.5 4764 580 pts/0 S 16:25 0:00 grep ntp
>
> and ntpq doesn't work
>
> I've commented out redhat's "restrict default ignore" line
> Here's ntp.conf:
>
> logconfig =sysall +syncall +clockall +peeral
>
> restrict 127.0.0.1
> restrict 10.10.8.0 mask 255.255.255.0 notrust nomodify notrap
>
> server clock.redhat.com
> server clock2.redhat.com
> server time.cachenetworks.com
> server louie.udel.edu
> server ntp.ourconcord.net
> server clock.nyc.he.net
>
> server 127.127.1.0
> fudge 127.127.1.0 stratum 10
>
> driftfile /var/lib/ntp/drift
> broadcastdelay 0.008
>
> authenticate yes
>
> keys /etc/ntp/keys
>
>
> Any help appreciated
> sean
>
Sean, I noticed that you are using the -p parameter, but I don't see where you
are stating the pid file.
Another option you may want to give a go to is the -g option.
-g Normally, ntpd exits if the offset exceeds the sanity limit,
which is 1000 s by default. If the sanity limit is set to zero,
no sanity checking is performed and any offset is acceptable.
This option overrides the limit and allows the time to be set
to any value without restriction; however, this can happen only
once. After that, ntpd will exit if the limit is exceeded.
This option can be used with the -q option.
