On 07/18/11 21:25, Daniel C. Sinclair wrote: > On Mon, Jul 18, 2011 at 9:11 AM, Theo de Raadt <dera...@cvs.openbsd.org> > wrote: > >> No thanks. >> >> I talked with a few people like this, and people who want to use rdate should >> be using it as rdate -n probably, and in that case, they should use ntpd -s >> instead. > > I find rdate_flags useful on my work laptop - I usually boot at my > desk while connected to the network where our internal ntp servers > are. It syncs, and then I take the laptop out to other > locations/networks where ntp is not accessible. Running ntpd isn't > useful then and I would have to kill it after it set the time. I
Why in the world would you kill it? If it can't talk to anything, ntpd just sits quietly in the background and does nothing bad. It isn't like it says, "oh, I can't find a server, so I'll just randomly alter the system time, that will teach him!" > How do other people keep correct time on their laptops when access to > ntp servers is intermittent? I just leave it at the default "pool.ntp.org", and when I am connected to net, it nudges the machine back towards correct time, when it isn't (and my netbook probably spends more time in use when NOT connected to the 'net than the people who came up with that name would ever imagine), I have never noticed ntpd running or not. The machine doesn't suck too badly, I never noticed any serious drift when it is off or unplugged. I see no problem. What problem do you think you see? Nick.
