Hi Timo, On April 3, 2003 04:13 pm, Timo Boettcher wrote:
[snipped] > > In my understanding ntpdate is now deprecated in favor of being rolled > > into ntpd itself. So it should really not be used anymore. > > So ntpdate will cease to exist? Any hint on why? No idea. > > Also, in my understanding, rdate is a one time thing when you execute it. > > As is ntpdate... > > > And must be put into a cron job to constantly keep your clock > > accurate. > > Whereas ntpd is a daemon that can be started and kept running. > > Doing the work of keeping your clock accurate automatically as it > > interogates time servers for you. > > But rdate/ntpdate do this, too or is there a difference between them? ntpdate is a one time thing too. And must be put into a cron job to continously keep the clock accurate. It just goes out to the Internet and gets the correct time. Just once. When it's executed. > ntpd can make the clock go faster/slower for continuosly going right. > Or did I get this wrong? ntpd will keep the clock accurate. As accurate as it can realistically be. By going out to the Internet every so often and updating the clock. You won't notice any slow down or speed up. It will be kept accurate to the second if not microsecond. > Also I heard once that use of all r* programs should be carefully > considered because of security reasons... does rdate count to this > group? Don't know about rdate but use of ntpd can, not neccessarily will, open up some security concerns. Personally I am not too worried about it because I run my computers behind a NAT firewall which sits between me and the Internet. But if you want to know more there are some good threads on the gentoo forum about security concerns with ntpd. Don't know which one's off the bat but there there. You might want to look under the Documentation Tips and Tricks for my ntpd instructions where some have commented on the security issue. Carlos www.internetsuccess.ca -- [EMAIL PROTECTED] mailing list
