RE: Starting NTP server: ntpd/usr/sbin/ntpd: invalid option -- p
Andrew Reid wrote:
> I'm afraid I'm not much of an expert on openntp. My first guess is
> that, as the system runs, the clock should sync up on its own, if
> ntpd is seeing valid servers and working properly.
If it were a 24x7 box, then yes. But, it's a virtual machine that I fire up,
hack around, and then shut it down.
> One potential issue, hinted at above, is that if eth0 is not
> up at boot-time, it's possible it can't find a reference source,
> and that's why it's not syncing at boot.
It came up this time:
20080616-184340 dpchrist@a64x23800p ~
$ ssh root@vd40r0
Last login: Sun Jun 15 21:49:19 2008 from 192.168.0.10
Linux vd40r0 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
20080616-183017 root@vd40r0 ~
# dmesg | grep eth0
eth0: registered as PCnet/PCI II 79C970A
eth0: link up
eth0: no IPv6 routers present
The clock is ~15 minutes slow.
> You might try /etc/init.d/openntp restart, while the network
> is in a known-good state, to see if that syncs it up.
20080616-183030 root@vd40r0 ~
# /etc/init.d/openntpd restart
Restarting openntpd: ntpd.
20080616-184610 root@vd40r0 ~
#
Now the clock is right. Thanks for the work-around. :-)
David
Reply to: