Network Time Protocol

[Mathias Koerber]

In article <Nov.6.13.28.58.1990.23381 at caip.rutgers.edu> nguyend at caip.rutgers.edu (Duc Nguyen) writes:
>
>  I've been trying to synchronize the clocks of sites on the Ethernet
>but could not figure out how to do this as accurate as possible. I

OK, I get the idea of synchronising the clocks of different hosts on a network,
and I think it is quite useful...

BUT: I know, that PROGRESS Database eg is *very* allergic against changes in
the system time. Especially setting the time BACKWARDS (even 1 sec) will kill
the server/broker process, because database integrity is based on the time.

There is a network version of PROGRESS around ( which I haven't used so far),
but I'd like to know, how a timed and networked PROGRESS can co-exist on a net.

	- inhibit timed from setting the clock backwards ? (sounds stupid)
	- run the progress server/broker from /etc/inittab
		(even stupider, all those broken sessions when it really happens)

	or is there a way (inside PROGRESS) to warn the broker and ALL clients
	of an pending time-change, so that all transactions are finished...
		*VERY* unlikely, timed would have to wait for PROGRESS to
		signal its OK...

And onw more question: Are there other packages, which depend on 
time-integrity? Even PROGRESS doesn't warn about this in the installation
notes. You only come across it, when you
	- either get the error-message
	- read the list of error messages in one of the many manuals..

Mathias

-- 
Mathias Koerber  | S iemens | Tel: +65 / 7473828-1852       | Fax: +65/7474331
2 Kallang Sector | N ixdorf | USA: uunet!nixbur!koerber.sin | nerv: koerber.sin
S'pore 1344      | I nformationssystems | EUnet: koerber.sin at nixpbe
* Packed with Power, SNIckers really satisfy  (or do theyAsk them gals :-) )*