-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 31 January 2004 10:14 am, Rodolfo J. Paiz wrote: > At 20:37 1/30/2004, you wrote: [...] > Lest others read Michael's post as suggesting that an ntpdate run every > two hours is a good thing for a /server/, I thought I should add some > comments. Most servers should run ntpd in order to keep time > synchronized as closely as possible, and most organizations should run > at least one ntpd server to which their computers can synchronize. > Please note that, in Michael's example, he is synchronizing to an > /internal/ server so hitting it every two hours is just fine. Correct, mine is an internal server. Syncing to a public server every two hours would not be a good thing. Sadly, using ntp -q in place of ntpdate is even worse, it appears to generate far more network traffic. - -- - -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) iD8DBQFAG9HUn/07WoAb/SsRAtPOAJ9dsuKOcp10Bm6IQJjEZMInwVg8VwCggR7z D8nBV486ncrmV1AwQn/hfZc= =Cw1y -----END PGP SIGNATURE-----
