-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 31 January 2004 05:42 am, Markku Kolkka wrote: > Michael Fratoni kirjoitti viestissÃÃn (lÃhetysaika lauantai 31. > > tammikuuta 2004 04:37): > > I missed the start of this thread, but does "ntpdate <server>" > > not do what you want? > > The ntpdate manpage says: > "The functionality of this program is now available in the ntpd > program. See the -q command line option in the ntpd - Network > Time Protocol (NTP) daemon page. After a suitable period of > mourning, the ntpdate program is to be retired from this > distribution" So it does. I haven't checked the man page for quite some time, and wasn't aware of this. Doing a little checking, ntp -q may provide the same functionality and more accuracy, but it's not quite as simple. It'll be a shame to see ntpdate removed. ntpdate is easier and more than accurate enough for the vast majority of systems. As near as I can tell, ntp -q requires ntp to be configured via /etc/ntp.conf, and then each call to ntp -q takes 30 - 60 seconds to complete. The only change needed from the default config file was the definition of a server line with the iburst keyword: "server 192.168.0.3 iburst" [root@snakebyte root]# time ntpd -q ntpd: time slew -0.010097s real 0m42.001s user 0m0.020s sys 0m0.030s [root@snakebyte root]# > As the subject says, the thread was about how to actually replace > ntpdate with a call to "ntpd -q". Yes, sorry for the confussion. The sheer volume of list mail of late has been a bit overwhelming. I've been deleting large message blocks unread with only a cursory look at the subjects. - -- - -Michael pgp key: http://www.tuxfan.homeip.net:8080/gpgkey.txt Red Hat Linux 7.{2,3}|8.0|9 in 8M of RAM: http://www.rule-project.org/en/ - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQFAG849n/07WoAb/SsRAhtZAJ9OlbmJnuCrVdUgg8/npgUrvBom0QCfXCMu H455U92vL4POMpuUKG92T9s= =gQpb -----END PGP SIGNATURE-----
