DragonFly bugs List (threaded) for 2005-02
ntpd Re: /etc/rc.d/rpcbind requires ntpdate
On Sat, Feb 19, 2005 at 09:46:17PM +0100, Joerg Sonnenberger wrote:
>On Sat, Feb 19, 2005 at 12:34:55PM -0800, Matthew Dillon wrote:
>> I mean, could we support the same original RC variables for specifying h
>> the remote host to pull the date from and then have the ntpd script
>> deal with it ?
>> The separation of the two functions (initial data sync and ongoing
>> correction) is important from an rc.conf perspective.
>I don't see a need from the administrative perspective of the separation.
>The rdate functionality in itself is useful, to set a time when working
>in a rescue system or because the box didn't have power for a long time.
>But doing a initial sync on boot without automatic correction seems to
>bit strange for me. Even the argument of not-permanently connection
>machines doesn't fit, the sync is better done in the up-scripts of ppp.
Well I just missed the rpcbind # REQUIRE: NETWORKING ntpd syslogd named ppp
patch today... but when I put it in "rcorder /etc/rc.d/*" comes up with
many errors. ...so I put it back.
I don't care about that right now. The problem I'm having is "ntpd -s"
on bootstrap, it doesn't happen. At first I thought it was semantics
in ntpd (8) and/or the handbook, but even with ntpd_flags="" or
ntpd_flags="-s" in rc.conf, rc.conf.local and /usr/local/etc/rc.conf,
ntpd doesn't start at boot.
The clock _was_ a long way off but "ntpd -s" from command line got it
fixed, and it still it won't start at boot with ntpd_flags="-s" and
xntpd_enable="YES" in /etc/rc.conf
# cat /etc/ntpd.conf
Am I missing something?
George Georgalis, systems architect, administrator Linux BSD IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:george@xxxxxxxxx