Thus spake Kevin Benton
On Fri, 7 Jan 2000, Ivan Baby wrote:
You are correct with your assessment of the Y2K status of NetServer 3.8.1. NetServer 3.8.1 is compliant through the year 2035. NetServer does not maintain its own clock but is dependent on an NTP server for the time. Has anyone asked the customer to display the time on their NTP server to see if it is correct?
If this is true, then why does a show time show a date of something in 1900 on both NetServers we're using? Why is the clock so far off? How can I get it set properly? My ARC's are doing just fine with NTP. NTP is being served by a local Linux box which is itself served by Ohio State University and Washington State University time servers (with a maximum 30 second difference) once every 24 hours. Are you saying my NTP is broken?
What's the command that you're using on your Linux box to sync with OSU and Washington State? The way you said it sounds like its being synced with ntpdate once a day, rather than letting ntpd run and adjust it constantly. I *believe* that ntpd will not serve as a time sync source for other systems if its not actively synced up with its own time sources...ie, running ntpdate once a day doesn't hack it. :) Perhaps you're aware of this and I'm misinterpreting your message. :) -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.