Linux-kernel mailing list archive 1998-25,: Re: Y2K

# Re: Y2K

Erik Corry (erik@arbat.com)
Tue, 23 Jun 1998 17:20:09 +0200

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: spacey@30minutes.netcreations.com: "Re: linux/alpha 2.0.30 - high uptime = hosed machine?"
- Previous message: Vojtech Pavlik: "Re: uniform input device packets?"
- In reply to: Y2K: "Y2K"

In article <Pine.LNX.3.95.980623082439.725A-100000@chaos.analogic.com> you wrote:
> How the leap second is supposed to work is similar to what we do
> here. Every night around midnight (actual time is not important), crond
> executes a task that does:

> rdate time-A.timefreq.bldrdoc.gov
> clock -w

> If somebody was writing a file at the time, the update time (UTIME) of the
> file could actually be earlier than its creation time, but only for that
> instant. If this was a problem, and I have only heard theoretical
> balderdash about it being a problem, no actual evidence of anything
> such as this even occurring; one could run `rdate` as such a high
> priority that it completes before anything else is allowed to run.

If you use gettime instead of rtime or nettime, then the
time will slowly adjust, and no sudden time travel is involved.
It's on Sunsite somewhere and it works very well for me.

    --
    Erik Corry

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu

- Next message: spacey@30minutes.netcreations.com: "Re: linux/alpha 2.0.30 - high uptime = hosed machine?"
- Previous message: Vojtech Pavlik: "Re: uniform input device packets?"
- In reply to: Y2K: "Y2K"