HP-3000 Systems Discussion wrote:
> It may have issues as a server/daemon.  If you just want to
> keep your 3000's clock periodically synchronized, try
> something like this:
> 
>> !job timesync,mgr.xntp;pri=cs
>> !ntpdate "a.b.c.d w.x.y.z"
>> !stream timesync.pub.xntp;in=0,12,0
> 
> substitute your favorite time servers addresses for a.b.c.d
> and w.x.y.z.
> 
> This is an "on-demand" synchronization every 12 hours (adjust
> to taste).
> 
> Jeff

Same thing I do on all my 3000s. 3000 doesn't work well (/at all) as an NTP
server, but periodically updating its time from an NTP source elsewhere
works just fine.

______________________/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_
  Chris Bartram        Sales: +44 1480-492400          Fax:+44 1480-414180
   ______                                              mailto:sales at
3k.com
  /__ |  \__________   Tech Support: +44 1480 492400   Me: chrisb at 3k.com
 /  / | / ________     mailto:support at 3k.com   WWW: http://www.3k.com
|  /_ |<  ______       PO Box 6003, Springfield VA 22150
 \ __)| \ ___          AIM and/or Yahoo IM: ChrisRBartram
  \______/Associates,  
_________________Inc._/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_

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