HP3000-L Archives

November 1999, 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 Bixby <[log in to unmask]>
Reply To:
Mark Bixby <[log in to unmask]>
Date:
Thu, 11 Nov 1999 20:36:15 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
Bonnie Roman wrote:
> An inhouse software was created for plant workers to punch in and out that is on
> the HP3000. But the plant workers tend to rely on the pc clock and use it as an
> excuse, if the HP-3000 punch-in says they're late (and the PC clock doesn't).
>
> Are there any programs that I could use to sync the pc's with the HP3000?

My XNTP/iX may be able to help:

        http://www.bixby.org/mark/xntpix.html

There are currently two ways you can run xntp on a 3000:

1) Run the ntpdate utility on your 3000 to do a one-time clock sync against an
external NTP time server (perhaps running on one of your PC network servers).
This is equivalent to obtaining the time from the remote machine and then doing
a single :SETCLOCK command.  If clock drift is a problem, you could run ntpdate
once a day/week/month/etc.

2) Run the xntpd daemon on your 3000 so other machines on your network can
query your 3000's clock.  Yours PCs would then run something similar to the
ntpdate command (I run a piece of freeware on my PC called Dimension4).

And if the bug documented on the XNTP/iX web page is ever fixed, there's a
third way you can configure your 3000:

3) Run the xntpd daemon on your 3000 to *continuously* sync your 3000's clock
to one or more external NTP time servers.

- Mark B.

ATOM RSS1 RSS2