Subject: | |
From: | |
Reply To: | |
Date: | Thu, 31 Jan 2002 09:36:09 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Mark Bixby wrote
You might check to see if there's anything useful in the CJCW CI variable to
differentiate between ntpdate success or failure.
If CJCW won't do it, you'll have to redirect the ntpdate output to a disk
file
and then parse it to determine success or failure.
---------------------------------------------
If NTP does not find a server suitable for synchronization it sets the
variable CJCW to 1. Which leads to the another question of why the
following NTP server I've been using for a year or so, hasn't been available
for several days.
US CA ntp-cup.external.hp.com (192.6.38.127)
Location: Cupertino CA (SF Bay area) 37:20N/122:00W
Synchronization: NTPv3 primary, HP-UX/Palisade-GPS
Service Area: West Coast USA
Access Policy: open access
Contact: [log in to unmask]
Note: no need to notify for access, go right ahead!
Perhaps someone at HP could ask around.
Mike Berkowitz
Guess? Inc.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|