Re: CVS commit: src/etc/rc.d

[Marc Balmer <marc%msys.ch@localhost>]

Am 06.08.2009 um 17:08 schrieb Marc Balmer:

> Am 06.08.2009 um 16:54 schrieb Perry E. Metzger:
>
> > Frank Kardel <kardel%netbsd.org@localhost> writes:
> > > Actually we can retire ntpdate in rc unless we are very tight on
> > > memory. ntpd_flags should add the -g flag. This allows  for a  big
> > > (time setting) initial (and only one time) step in ntpd.
> >
> > I was made aware of that a few days ago.
> >
> > If we go that route, however, we will have to move ntpd to start much
> > earlier (where ntpdate currently runs), because various tools like  
> > the
> > kdc stuff require that the time be properly set before they execute.
>
> I have a question here:  Does that mean that we always have to run  
> ntpd if we want exact time at startup?  Or has ntpd a mode where it  
> syncs the time one time and then exit?
>
> If it has not, maybe ntpdate should stay.

I can answer it myself ;)  it can... sorry for the noise...

> - Marc
>
> > I'm willing to do that for -current but not for 5.0 (the fixes now in
> > -current are being pulled up.)
> >
> > > This is the ntpdate functionality with ntpd normally continuing
> > > afterwards. ntpd is fine when the network is up with loopback
> > > interfaces only. It will discover interfaces going up/down
> > > automatically and re-trigger name resolution when new interfaces  
> > > come
> > > up and unresolved dns-names still exist.
> >
> > That seems like quite a good thing. We should probably do that,  
> > moving
> > ntpd much earlier in the system startup and making kdc etc. depend on
> > ntpd instead of ntpdate. Are you willing to do the work? I don't have
> > time for some days.
> >
> > Perry
> > --
> > Perry E. Metzger                perry%piermont.com@localhost