Maybe this is a silly question, and I sort of feel I should know the 
answer, but...  why doesn't chmod in solaris change the time stamp of a 
file when you do an ls?

How can I determine the time a file was chmod'd ?

Thanks :)

Michelle

Michelle wrote:
> Maybe this is a silly question, and I sort of feel I should know the 
> answer, but...  why doesn't chmod in solaris change the time stamp of a 
> file when you do an ls?
> 
> How can I determine the time a file was chmod'd ?
> 
> Thanks :)
> 
> Michelle

oh I think ls -lac works

In article <7nbwk.545$yS5.22@edtnps83>, Michelle <newsgrps0001@mst.ca> 
wrote:

> Michelle wrote:
> > Maybe this is a silly question, and I sort of feel I should know the 
> > answer, but...  why doesn't chmod in solaris change the time stamp of a 
> > file when you do an ls?
> > 
> > How can I determine the time a file was chmod'd ?
> > 
> > Thanks :)
> > 
> > Michelle
> 
> oh I think ls -lac works

There are three times tracked by the file's inode on UFS file 
systems--ctime (time since the file's inode was changed), mtime (time 
since the file was last modified), and atime (time since the file was 
last accessed).  By default, ls show the time last modified.  As you've 
found out, it can also show other times.  Filesystems can be mounted 
with noatime to prevent atime from being updated with can be a 
performance hit on high-volume filesystems.  Note there is no place 
where UNIX tracks the date/time a file was created.

-- 
DeeDee, don't press that button!  DeeDee!  NO!  Dee...
[I filter all Goggle Groups posts, so any reply may be automatically by ignored]