[ale] ntp

[Joseph A. Knapka]

What exactly is the time problem? How far off are the clocks on the
machines that won't sync? If it's more than an hour or so, I believe,
ntpd will just refuse to sync; I assume this is to avoid getting
bogus time data from a misconfigured server. You need to either run
ntpdate first to bring the local clock in line with the server, or else
there's a magic option to ntpd, -g I think, that forces it to use the
configured server no matter how far off the local clock is.

Good luck,

-- Joe

Jeff T wrote:
> 
> In order to keep all the UNIX hosts on my network running at the
> same time I use ntp.  I use a LINUX server to act in client mode
> to an external clock server and then all my UNIX workstations function
> as clients to the LINUX server.  I have been running it successfully
> for about 8 months.
> 
> This morning one of the developers informs me there is a time problem.
> I have been trying to solve it ever since.  The ntpd daemon starts
> up okay and using ntpdc on the hosts seems to give me proper responses.
> I have rebuilt ntpd from source on the server and on my client
> to no avail.  I downloaded automachron for a Windows client and it
> will sync with the LINUX server but none of my UNIX hosts will.
> 
> The UNIX hosts are mostly Red Hat Linux and IRIX 6.5.x.  Anyone have
> any pointers that I should look at?
> 
> Jeff
> 
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.

-- Joe Knapka
"It was just a maddened crocodile hidden in a flower bed. It could
 have happened to anyone." -- Pratchett
// Linux MM Documentation in progress:
// http://home.earthlink.net/~jknapka/linux-mm/vmoutline.html
* Evolution is an "unproven theory" in the same sense that gravity is. *
--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.