-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-10-04 at 21:04 +0100, William Gallafent wrote:
On Wednesday 04 October 2006 20:02, Carlos E. R. wrote:
In other words, ntpd is designed for machines with permanent network connections.
At the risk of turning this thread circular, ...
Even though that's true, what is the reason _not_ to start ntpd (rcntp start) just after a network connection is started, and stop it again just before the network connection is shut down?
It is possible, of course, but ntpd may not have time to complete its job.
(Forgive my ignorance, but) does 'rcntp start' effectively perform an 'ntpdate' command, then start ntpd?
That's what it does, in fact. You can also call "rcntp ntptimeset", it does the same as "ntpdate" but reading the config file ntpd uses. Let me try to clarify things. The ntp daemon does quite more than checking the time periodically and adjust the system time; if it did, your approach would be correct. More or less, it checks the time, adjust the clock speed so that it slowly gets in sync with the real time out there, and then adjust the speed back again so that it maintains in sync from then on, but doing continuous adjustments as soon as it detects a difference. Lets us make an educated guess, and think out what will happen if the network connectivity is intermittent (I haven't studied the code). Suppose the system clock is slow. There is network, so ntpd adjusts it to go faster instead, till it catches; then the network goes off, and... what? The daemon can't know when it catches the real time and thus when to slow it a bit. If the daemon has been running for sufficient time (days) it will know what is the exact adjustment the clock needs and leave it there hopping for the best, till it can read outside time again. If it doesn't know the needed factor, it will probably leave the original value and exit after trying for a while. As I said, this is an educated guess, but I bet you my stipulated amount for sure things (two cents) that the above scenario is correct :-)
KNetworkManager allows commands to be run at "Link Up" and "Link Down", so why not do it there? What are the security implications of making the rcntp script suid root? Hmm, .....
Scripts can not be made suid, I understand. Or if they can they don't work. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFJD/xtTMYHG2NR9URAiQoAJwPI5XbTEdRpXB/bcy2TF2ok1n6bACfdOTP 5pDJwIFA26IVkNnC+VrRlC4= =5ql4 -----END PGP SIGNATURE-----