NTPD

[Alexey Fadyushin]

I recommend to use NTPD on all your RedHat servers so the servers will 
be able to sync time with each other. This will eliminate the common 
point of failure which is possible in the configuration with ntpdate 
when the timesource_server used for ntpdate will have wrong time. In the 
situation when all sever prowide synchronization to each other wrong 
time on any one of them will bw corrected by time syncronization from 
other servers.
Just say in the NTPD configuration on RedHat and Solaris servers that 
those servers are peers to each other using 'peer' directive. There is 
no need to be connected to internet to use NTP. However in this case you 
  will use not the exact time fron Internet time servers, but some mean 
time of majority of your NTP servers.
In the windows XP configuration list them all as NTP servers so the XP 
clients will not get out of sync if any (but not all) of your NTP 
servers fail.

Alexey Fadyushin.
Brainbench MVP for Linux.
http://www.brainbench.com


McDougall, Marshall (FSH) wrote:
> Charlie.
> 
> In our situation, we have 1 server acting as the time source and I cron a
> nightly script that syncs the clocks off of the one.  The time source
> machine is running ntpd and my cron is just "ntpdate -u
> my_timesource_server".
> 
> Nothing fancy and it works just fine to keep all the local clocks in sync.
> 
> Regards, Marshall
> 
> -----Original Message-----
> From: Charlie H. Thompson [mailto:cthompson at tsidefense.com] 
> Sent: Thursday, December 23, 2004 4:43 PM
> To: redhat-list at redhat.com
> Subject: NTPD
> 
> 
> I have a closed peer-to-peer network running Red Hat 9.0, Solaris 8, and
> Windows XP.  There is no connection to the internet.  There is a great need
> to have all computer time synced.
> 
> Is it possible to configure one of the Red Hat 9.0 servers as an NTP server
> for the others without connecting to a network?  If so, where can I go to
> find out how?
> 
> Charlie
>