-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-02-22 at 08:14 -0800, Kai Ponte wrote:
If you're only after adhoc/on-demand time-sync, why not just run ntpdate?
Well, a few reasons:
First, I cannot find any good documentation.
No? Did you look well? "man ntpdate" says that the main documentation is in "/usr/share/doc/packages/xntp-doc". In there, you find two directories: NTP-FAQ and html - the names are self-explanatory. I fact, if you run "locate ntpdate" you find "/usr/share/doc/packages/xntp-doc/html/ntpdate.html", which is a fairly good doc.
Second, it seems to do the same as ntp start.
Not really. The script call "ntp start" calls ntpdate, and then it starts the "ntpd" daemon, which remains running till you stop it or halt the computer. Remember it needs a permanent network connection. In fact, the script call "rcxntpd ntptimeset" is the one that really sets the clock once and exits, not "start". And it use the "/etc/ntp.conf" configuration file, so it is far easier to call than ntpdate.
Third, it appears to be depricated from what I can find on google.
So they have been saying for some years now: I have stopped paying attention to that.
Fourth, I still have to su to run it.
Same as for "ntp start".
Now, it would be nice if changing the system date/time on a single-user system could be made a non-root action.
Never! Use 'sudo' if you must. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD/K4gtTMYHG2NR9URArBWAJ4yJy0I8B8+aP1g3yj+B+ArpcGu6QCgkL0P qs7MPXd/F1PsPn2etOdsPI8= =A0cv -----END PGP SIGNATURE-----