Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix-wizards
Subject: Re: File times in 4.[23]
Message-ID: <3043@umcp-cs.UUCP>
Date: Thu, 21-Aug-86 01:42:49 EDT
Article-I.D.: umcp-cs.3043
Posted: Thu Aug 21 01:42:49 1986
Date-Received: Thu, 21-Aug-86 04:14:19 EDT
References: <7053@boring.mcvax.UUCP>
Reply-To: chris@umcp-cs.UUCP (Chris Torek)
Organization: University of Maryland, Dept. of Computer Sci.
Lines: 38

In article <7053@boring.mcvax.UUCP> jack@mcvax.uucp (Jack Jansen) writes:
>... we noticed that the behaviour of file access times under 4.3
>is not according to the manual. ...
>Manual: access time changed by read, write and some others.
>	modify time changed by write
>	creation time changed by link, chmod, etc.

Hold!  /There is no creation time!/  `ctime' is `last change' time.
It should be updated any time the disk inode is changed in any way,
so that the file is properly backed-up.

>4.2:	access time changed by read *only*.
>	modify time changed by write
>	creation time changed by link, *but not chmod*.

If chmod does not update inode ctimes, it is rather seriously broken.
A full restore of a file system could leave many files with the wrong
modes.

>4.3:	access time changed by read *only*.
>	modify time changed by write
>	creation time never changed (except by creation, of course).

This last is most certainly untrue.

>Especially the fact that the access time doesn't change on write
>looks like a bug to me....	

No: here the manual must be in error.  `access' means `read', more
or less.

The `ls' manual is buggy; it claims that `ls -c' sorts on, and/or
prints, file creation times, when in fact no such times are available.
Are there others that make similar claims?
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1516)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu