On 11/27/01 at 12:45 PM, Matt Schalit <[EMAIL PROTECTED]> wrote: > Jeff Newmiller wrote: > [snip] > > > > xntpd steps the clock on my unix box every so often, > > > but it slews it every day. Not sure what your seeing. > > > > David is referring to a startup phenomenon. Read the > > manpage for ntpdate. > > I read that one, and it refers to how ntpdate steps or slews. > I don't see any mention that xntpd behaves like ntpdate.
It goes like this: You boot your machine. The startup script for xntpd runs ntpdate to set the system clock (and the kernel clock). It does this in such a way so that the time is set right away, even if it is hours or days off. Then xntpd runs, and it only slews the clock forwards or backwards to match the current time server. It may go faster or slower, but it should never (as far as I know) "jump" in time - this is so that running processes don't get confused or fail. After ntpdate runs during boot, its job is (normally) completed, and as long as xntpd runs, it's not needed again. > I'd like to be more help on the Linux side of things, but > the whole date/time subystem in Oxygen is broken w.r.t. > timezones, so it's a disaster for me to even try. Oxygen date/time shouldn't be broken, especially with regards to Central Time (my local time zone). I figure enough things come set to Mountain Time (California) or Eastern Time (Massachussetts, etc.). About time something came set to Central Time :) I'll probably look at replacing rdate with ntpdate - to get away from the time service. -- David Douthitt UNIX Systems Administrator HP-UX 10.2 & 11.0, Red Hat Linux, Unixware 2.x [EMAIL PROTECTED] _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
