I think ntp is the wrong tool for the job here. ntp isn't for keeping you clock about right, its for when you want yor clock to be extremly acurate. You should have a working clock to startwith (i.e. no harware errors or miss-configurations) Unless you force it to (-g I think), ntpd will usually kill itsself if it detects an error with your clock (i.e. if it goes to far out of sync it will give up.)
Just saying, 'coz ntpd seems to be a slightly missused tool. Rob On Thu, Jul 03, 2003 at 12:13:39AM -0500, Christopher Egner wrote: > Alright, perhaps I'm a bit lost on this. My clock always runs off about > 20 to 30 minutes after a day or so. Only in linux though. I figured I'd > start using ntpd. However, I can't seem to figure out how to configure a > timezone for it. Any help here would be great. > -- > Christopher > > In 1968 it took the computing power of 2 C-64's to fly a rocket to the > moon. Now, in 1998 it takes the Power of a Pentium 200 to run Microsoft > Windows 95. Something must have gone wrong. > > > -- > [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
