home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!das-news.harvard.edu!cantaloupe.srv.cs.cmu.edu!crabapple.srv.cs.cmu.edu!andrew.cmu.edu!cs4w+
- From: infidel+@CMU.EDU (Charles William Swiger)
- Newsgroups: comp.sys.next.bugs
- Subject: Re: NFS mounts -- time stamp problems?
- Message-ID: <QfNRoLC00YUnJYCTBk@andrew.cmu.edu>
- Date: 26 Jan 93 14:53:43 GMT
- Article-I.D.: andrew.QfNRoLC00YUnJYCTBk
- Distribution: comp
- Organization: Senior, Chemistry, Carnegie Mellon, Pittsburgh, PA
- Lines: 33
- In-Reply-To: <1993Jan25.191725.23058@imada.ou.dk>
-
- Excerpts from netnews.comp.sys.next.bugs: 25-Jan-93 NFS mounts -- time
- stamp pr.. by Thorbjoern Andersen@imad
- > Apparently, date stamping works incorrectly when setting stamps
- > explicitly, instead of inheriting the dates from the file system.
- >
- > Touching a file yields a date of January 1 1970, which is somewhat
- > incorrect. I *think* this is date Zero, but why should that be?
-
- 1/1/70 was chosen to be the "epoch" for Unix filesystems. All of the
- timestamps used count in seconds from epoch to the current time.
-
- (Some trivia: the values are stored in 4-byte longs, meaning that the
- time system will break in the year 2038.)
-
- > Anybody got any suggestions for circumventing this problem?
-
- I suspect that one or more machines on your network are having problems
- with their clocks. Make sure that you are using the Network Time
- Protocol on all of the machines on the network. NTP was explicitly
- designed to help keep distributed filesystem's timestamps correct
- between machines sharing files.
-
- Consult your System's Administration manuals....
-
- -Chuck
-
-
-
- Charles William Swiger -- CMU...*crunch*! | "Foosh. Aaughh!!"
- ------------------------------------------+ "Foosh. Aauuggghh!!"
- AMS & normal mail: infidel@cmu.edu | "Cold spray deodorant...."
- Failing that: cs4w+@andrew.cmu.edu |
- NeXTmail: chuck@mon.slip.andrew.cmu.edu | -- Opus, Bloom County [RIP]
-