On Monday 10 April 2006 21:36, Leendert Meyer wrote:
On Monday 10 April 2006 21:25, Greg Wallace wrote:
On Monday, April 10, 2006 @ 1:47 PM, Leendert Meyer wrote:
On Monday 10 April 2006 20:39, Richard Bos wrote:
Have a look here: http://susewiki.org/index.php?title=Schedule_cron_daily
From that file:
In SuSe 9.3 touch modifies all 3 access times to the touch time if used without the -t flag!!
The same for SUSE 10.0 - I just checked. :)
Cheers,
Leen
If you wouldn't mind, just to satisfy my own curiosity, what are the 3 timestamps that are being touched? In various other threads on this list, I came away with the impression that there were only two timestamps being maintained by any of the underlying file systems (Reiser, EXT2, EXT3, etc.). Is this not true? Are there actually 3 timestamps being maintained for a single file/directory at file system level, or, in this case, is it done via some software implemented mechanism?
I forgot to answer your other question: I always understood that there are 3 timestamps maintained in the filesystem: creation, access and modification. As I learned today, the creation time is actually the time of the last state change. And it must be part of the filesystem (on disk), how would it else work across e.g. reboots?
Here's the output from test I did: ---<cut>--- leen@ws-03:~> f="test.txt"; rm -f $f; echo "a" > $f; stat $f; sleep 10; touch $f; stat $f File: `test.txt' Size: 2 Blocks: 8 IO Block: 4096 regular file Device: 308h/776d Inode: 326689 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ leen) Gid: ( 100/ users) Access: 2006-04-10 21:33:33.000000000 +0200 Modify: 2006-04-10 21:33:33.000000000 +0200 Change: 2006-04-10 21:33:33.000000000 +0200 File: `test.txt' Size: 2 Blocks: 8 IO Block: 4096 regular file Device: 308h/776d Inode: 326689 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ leen) Gid: ( 100/ users) Access: 2006-04-10 21:33:44.000000000 +0200 Modify: 2006-04-10 21:33:44.000000000 +0200 Change: 2006-04-10 21:33:44.000000000 +0200 leen@ws-03:~> ---<cut>---
Cheers, Leen