I did sync finally..
[EMAIL PROTECTED] [/usr/local/man]# 30 > /usr/local/sbin/ntpd -s -d -f /usr/
local/etc/ntpd.conf
listening on 10.20.0.16
listening on 10.20.0.29
ntp engine ready
reply from 209.51.161.238: offset 0.005419 delay 0.016668, next query 6s
reply from 209.51.161.238: offset 0.005236 delay 0.016233, next query 6s
reply from 209.51.161.238: offset 0.005288 delay 0.015782, next query 9s
peer 209.51.161.238 now valid
reply from 209.51.161.238: offset 0.005271 delay 0.016006, next query 9s
reply from 209.51.161.238: offset 0.005550 delay 0.015967, next query 7s
reply from 209.51.161.238: offset 0.005616 delay 0.016308, next query 7s
reply from 209.51.161.238: offset 0.005714 delay 0.015999, next query
30s
reply from 209.51.161.238: offset 0.005995 delay 0.016138, next query
32s
adjusting local clock by 0.005288s
reply from 209.51.161.238: offset 0.001272 delay 0.016006, next query
301s
reply from 209.51.161.238: offset 0.004713 delay 0.016379, next query
307s
reply from 209.51.161.238: offset 0.008287 delay 0.016782, next query
307s
adjusting local clock by 0.005550s
clock is now synced
# ntpdate -d 10.20.0.16
1 Jul 15:19:01 ntpdate[2017]: ntpdate 4.2.0-a Sun Feb 24 16:32:49
UTC 2008 (1)
transmit(10.20.0.16)
receive(10.20.0.16)
transmit(10.20.0.16)
receive(10.20.0.16)
transmit(10.20.0.16)
receive(10.20.0.16)
transmit(10.20.0.16)
receive(10.20.0.16)
transmit(10.20.0.16)
server 10.20.0.16, port 123
stratum 2, precision -21, leap 00, trust 000
refid [10.20.0.16], delay 0.02599, dispersion 0.00000
transmitted 4, in filter 4
reference time: cc15016a.d35167ff Tue, Jul 1 2008 15:18:02.825
originate timestamp: cc1501a5.98b65fff Tue, Jul 1 2008 15:19:01.596
transmit timestamp: cc1501a5.98d9b8dd Tue, Jul 1 2008 15:19:01.597
filter delay: 0.02605 0.02599 0.02599 0.02599
0.00000 0.00000 0.00000 0.00000
filter offset: -0.00067 -0.00072 -0.00072 -0.00072
0.000000 0.000000 0.000000 0.000000
delay 0.02599, dispersion 0.00000
offset -0.000727
1 Jul 15:19:01 ntpdate[2017]: adjust time server 10.20.0.16 offset
-0.000727 sec
On Jul 1, 2008, at 1:28 PM, Steve Bertrand wrote:
B. Cook wrote:
Hello All,
Hey,
[EMAIL PROTECTED] [/usr/local/etc]# 32 > ntpdate -b clock.nyc.he.net
1 Jul 12:49:57 ntpdate[70917]: step time server 209.51.161.238
offset 358.732506 sec
Why when it was running did it not update the clock on the server?
My first guess, which is only a guess, is that your secure level is
too high for this to work. If your securelevel is set above zero,
then your clock can only be adjusted by a maximum of one second
(please correct me if this has changed since 4.x).
Check the output of:
sysctl -a kern.securelevel
Strange thing two:
From a different computer I can not get the time from the server
running openntpd.
# ntpdate -b 10.20.0.16
1 Jul 12:50:23 ntpdate[679]: no server suitable for synchronization
found
Have you confirmed that a clock server runs on that IP? Is the IP
reachable?
If securelevel still has its place with affecting time changes, I'd
try 'breaking' that to see if the time will actually update. Note
that securelevel must be changed via a startup variable of some
sort, and a reboot is required.
Then I would proceed to ensure that 10.20.0.16 is actually running a
timeserver that the network can reach.
Steve
--
B. Cook
Network Analyst
Poughkeepsie City School District
Mobile: 845.264.5827 | Desk: 845.451.4791
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
