Thanks Bill, Darryl, Bret & Jim. This is precisely the type of information
I was looking for.
Thanks,
Mike
> -----Original Message-----
> From: Bill Carlson [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 17, 2000 8:27 AM
> To: [EMAIL PROTECTED]
> Subject: Re: XNTPD questions
>
>
> On Fri, 14 Apr 2000, Mike Lewis wrote:
>
> >
> > I'm just setting up xntpd for the first time. I believe I
> have the server
> > piece running and syncing to the various time servers.
> However, I have some
> > questions that I've not yet been able to find the answers to:
> >
> > 1) Now that I have one machine on my LAN syncing to an
> outside source, how
> > do I configure the other Linux boxen to sync to the local
> time server rather
> > than the ones on Internet ?
>
> In the conf file for xntpd, you just say:
>
> server <lan time server>
>
> and start xntpd. Remove any of the broadcast stuff, unless
> you really want
> to use it.
>
> >
> > 2) Suppose you have several LANs that you would like to
> sync time on to
> > some standard (not necessarily each other). Wouldn't it be
> better to have
> > one of the LANs as a 'master' NTP server (which updates to
> some stratum 2
> > server) and have the remainder of the LANs sync to that server ?
>
> The way xntpd works, it would be better to point have several
> points of
> reference. That way, if one goes 'insane', it will be ignored
> in favor of
> the majority opinion as to what time it is.
>
> I had a setup where I had 4 boxes that sat on the Net. I then had the
> company LAN sitting behind one of those 4 boxes. I setup 3 of the Net
> machines to point to several stratum 2 boxes and then pointed
> the inside
> LAN machines to those 3 boxes (they were all Unix hosts at
> that point). So
> unless I lost the Net altogether, time would keep insync if 1
> or 2 hosts
> were down or 'insane'.
>
> The traffic from xntpd is pretty light, so unless you have to
> pay for bits
> transferred I'd go with a setup like the above.
>
> One setup catch, xntpd won't start adjusting time if the
> clock isn't close
> to the correct time, I believe the range is adjustable. In
> any case, it is
> good to make sure ntpdate is called correctly in
> /etc/rc.d/init.d/xntpd, I believe recent versions of RH look
> for a list of
> time servers in /etc/ntp/step-tickers, but you have to create
> that file
> yourself.
>
> >
> > 3) From a previous message posted to the list, I
> understand that by using
> > "NET TIME /SET /Y \\linuxboxen" (on WinBoxen) this will
> set the time to the
> > 'master' NTP server on the LAN. When I try this on Win95, I get:
>
> I seem to remember a ntp client for Windows, you might want
> to look into
> that as it can adjust for clock drift on the local RTC.
>
> HTH,
>
> Bill Carlson
> ------------
> Systems Programmer [EMAIL PROTECTED] | Opinions are mine,
> Virtual Hospital http://www.vh.org/ | not my employer's.
> University of Iowa Hospitals and Clinics |
>
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
