ADSM-L

Re: AW: AW: HP client oddity

2000-01-07 07:56:14
Subject: Re: AW: AW: HP client oddity
From: Richard Sims <rbs AT BU DOT EDU>
Date: Fri, 7 Jan 2000 07:56:14 -0500
Just a tech note regarding timestamps on file system objects in
Unix systems...

In traditional Unix systems, file system objects each have three
timestamps: atime, mtime, and ctime.  The first two reflect Access
time and Modification time, and one expects the third to reflect
the object Creation time - but that is not the case: ctime instead
basically reflects when the object's attributes were changed, the
data remaining unchanged.  So ctime reflects "inode change time".
Here is an extract from the Solaris man page on the stat struct,
which summarizes things (the Solaris man pages usually being more
illuminating than the AIX man pages, alas):

     st_atime  Time when file data was last accessed.  Changed by
               the  following  functions:   creat,  mknod,  pipe,
               utime, and read.

     st_mtime  Time when data was last modified.  Changed by  the
               following  functions:   creat, mknod, pipe, utime,
               and write.

     st_ctime  Time when file status was last  changed.   Changed
               by  the following functions:  chmod, chown, creat,
               link, mknod, pipe, unlink, utime, and write.

 Richard Sims, BU
<Prev in Thread] Current Thread [Next in Thread>