home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.shell
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!haven.umd.edu!decuac!pa.dec.com!decprl!decprl!boyd
- From: boyd@prl.dec.com (Boyd Roberts)
- Subject: Re: RM LOGIC
- Message-ID: <1992Nov6.132332.218@prl.dec.com>
- Sender: news@prl.dec.com (USENET News System)
- Nntp-Posting-Host: prl313.prl.dec.com
- Organization: Digital Equipment Corporation - Paris Research Laboratory
- References: <1992Nov2.131722.27419@polari> <MERLYN.92Nov2131214@romulus.reed.edu> <MERLYN.92Nov3110424@romulus.reed.edu> <1559@rand.mel.cocam.oz.au>
- Date: Fri, 6 Nov 1992 13:23:32 GMT
- Lines: 27
-
- In article <1559@rand.mel.cocam.oz.au>, twp@rand.mel.cocam.oz.au (Tony Payne CSD) writes:
- >
- > Nor have I ever seen a UNIX beastie like that. It seems to boil down to the
- > fact that most files don't ever have their inode changed, except when they are
- > created. So in most cases inode change time corresponds to creation time.
- > Just another idiotic historical hangover.
- >
-
- Well it always good to add more noise into the signal. The inode change
- time changes when the inode data changes. Most of the time this occurs
- on writes, but also ocurrs on chmod, chown etc but they are probably
- less frequent. So the ctime would indicate a files creation time in
- this one case alone: a file that has only had creat operations.
-
- So, you want an example:
-
- prl313 ; work/sheraton/walk hosts
- 721054655 721054676 721054655 664 - hosts
-
- What we see here is that the ctime and mtime are equivalent, whereas
- the atime is somewhat later. I clicked on write in `sam' at 721054655
- and then read the file 21 seconds later at 721054676.
-
-
- Boyd Roberts boyd@prl.dec.com
-
- ``Not only is UNIX dead, it's starting to smell really bad.'' -- Rob Pike
-