-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-02-23 at 08:25 +0100, Per Jessen wrote:
True enough. But it is pointless to start it then, anyway :-)
Not quite. I guess it depends - if I would like my system to be sync'ed to a precise clock, and my network connection is intermittent (dial-up or just unstable), I would still just start ntpd and forget about it. That way I would achieve a situation of "mostly synced clock" without giving it any more thought.
I think that ntpd polls the server at long intervals, once it is in sync. That means that it may well happen that the poll happens when the connection is down (and it will complain), and that it doesn't poll when the connection is open. It would be far better to call either ntpd or ntpdate from the "/etc/ppp/ip-up.local" script automatically when the connection goes up, and removing the service, again automatically, when it goes down. That's what I have there, by the way. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD/beztTMYHG2NR9URAhmaAJ4jQ0CIt8daU0RdnJKJjqpRQAQmLgCeOcGI 6FCttPJ+EmSsdyhf0hjyhRU= =nR5z -----END PGP SIGNATURE-----