On Tue, Sep 10, 2002 at 10:58:36PM +0100, Duncan Greenwood wrote:
> According to the docs for the stat system call, a write should
> update both mtime and ctime. I can't see how Oracle could
> avoid this this happening, even intentionally.
>
> st_atime
> Time when file data was last accessed. Changed by the following
> functions: creat(), mknod(), pipe(), utime(2), and read(2).
>
> st_mtime
> Time when data was last modified. Changed by the following
> functions: creat(), mknod(), pipe(), utime(), and write(2).
>
> st_ctime
> Time when file status was last changed. Changed by the following
> functions: chmod(), chown(), creat(), link(2), mknod(), pipe(), unlink(2),
> utime(), and write().
>

You are correct. I think the procom filer has a bug somewhere in
this area and I will be pursuing that.

> There are some options to the NFS mount command that can
> affect how these timestamps are handled. What is the full mount
> command you are using, or the relevant line from /etc/vfstab
> for the filesystem in question ?
>

I am not aware of any options which affect this behaviour
under solaris, but I will check. Thank you for the pointer.

Regards,
pdg

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=