On Mon, 05 Apr 1999 08:46:38 +0930, Ian West i...@apdata.com.au said:
Thanks for the response, there isn't per chance an option to turn this
on is there ?
The way programs are executed (by intention) does not run through the
code path which would touch the access time. The POSIX.1
The way programs are executed (by intention) does not run through the
code path which would touch the access time. The POSIX.1
specification, IIRC, requires that the atime be updated when the
program exits -- this would be very inefficient to do in our VM
system.
It requires only _marking_ for
Is it normal for atime not to be set on execution of a file ?
I should have thought this would class as an access ?
(I do not have the filesystem mounted -o noatime :-)
This may be questions, but I am running current...
Thankyou.
To Unsubscribe: send mail to majord...@freebsd.org
with
Is it normal for atime not to be set on execution of a file ?
I should have thought this would class as an access ?
It's normal in FreeBSD, although this breaks POSIX.1 conformance.
Bruce
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the
Bruce Evans wrote:
Is it normal for atime not to be set on execution of a file ?
I should have thought this would class as an access ?
It's normal in FreeBSD, although this breaks POSIX.1 conformance.
Bruce
Thanks for the response, there isn't per chance an option to turn this
on is
