HP3000-L Archives

August 2009, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Ranft <[log in to unmask]>
Reply To:
Mark Ranft <[log in to unmask]>
Date:
Fri, 14 Aug 2009 12:43:35 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (21 lines)
My opinion on NTP is different.  However, I do not use the HP3000 systems as
the NTP server.  Instead I use a corporate NTP server (probably on a unix
box, which is synchronized to a government time server.

The ntp client executable that I have is called NTPDATE.  I think it is
included in Mark Bixby's routines.  I use it in a command file to compare
the system date and time to the server.  If it is more than 30 seconds off,
I automatically use the same program with a different parameter to adjust
the time.  If it is more than 45 seconds off, I send a message/page, as
something is up (like a time test or a reboot and someone forgot to set the
hardware clock.)  I have my proactive HP3000 monitor doing this on all my
systems every 10-20 minutes.

Before a patch, I had seen heavily loaded systems experience time drift.
This routine was a life saver.

Mark R

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2