Fred K Ollinger on Mon, 13 Jan 2003 15:10:35 -0500 |
ntpd is pretty easy for all distros I've used including rh. > >Whose ntpd documentation is confusing? :^> > > > >Since the Red Hat Linux way has already gone past, here's the NetBSD > >version. In /etc/rc.conf, add: > > > >ntpdate=YES > >ntpd=YES BSD simplicity can be nice. One can either use symlinks (to /etc/rc* or chkconfig (rh) or update-rc.d (debian) to get same effect). > >Because /etc/rc.d/ntpd requires DAEMON and /etc/rc.d/ntpdate only > >requires NETWORKING[1], ntpd won't start till after ntpdate has run > >(important, because you can run ntpdate while ntpd is running on the > >localhost; they can't both get at the clock at the same time). > > > >Then, in /etc/ntp.conf, add: > > > >server a.b.c.d > >server w.x.y.z Adding a few server lines then doing: /etc/init.d/ntpd restart has worked for all the linux distros I've used: rh and debian. > >There's no need for Red Hat's silly step-tickers file, since this: Seroius question: what is that file? > > > > awk '/^server[ \t]*127.127/ {next} \ > > /^(server|peer)/ {print $2}' < /etc/ntp.conf > > > >will get you your servers and peers. (/etc/rc.d/ntpdate on NetBSD > >does exactly this.) Fred Ollinger _________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
|
|