-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-02-22 at 21:17 +0100, Per Jessen wrote:
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.
Perhaps as a last comment - ntpd does't actually need a permanent network connection. When it has one, it'll try to sync with whichever server you have specified, and when it doesn't have a connection, you can configure it to pretend the local clock is good enough (I think this is the default SUSE config).
True enough. But it is pointless to start it then, anyway :-)
And it use the "/etc/ntp.conf" configuration file, so it is far easier to call than ntpdate.
Actually, I think the advantage of ntpdate is that you can use without a fully configured ntpd. "ntpdate <server> works fine regardless of what you've got in ntp.conf.
Well, yes, and no. The only thing needed for 'rcxntpd ntptimeset' to work is that '/etc/ntp.conf' has the servers defined, the rest is ignored. It is a trick done by SuSE, not the work of ntpdate. In other words, the script extracts the server names from the configuration file, then calls ntpdate with the servers in the command line ;-) - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD/QwktTMYHG2NR9URAoj3AJ9eFUxR0YRuLcOBSgFjix0bjp4DaACeJ/cK M1OsTj3dOhV8IZp0clxUrGA= =zVGc -----END PGP SIGNATURE-----