diff options
author | kensmith <kensmith@FreeBSD.org> | 2005-02-02 00:21:38 +0000 |
---|---|---|
committer | kensmith <kensmith@FreeBSD.org> | 2005-02-02 00:21:38 +0000 |
commit | 4130080e12ab49a659e616322a16e9db22726595 (patch) | |
tree | 0e539d0e3639c3979c39b66d95f7f7da60ebff96 /usr.bin/kdump | |
parent | 4ab36f5f9693a3b43be9e19c6c45db0b6f095edf (diff) | |
download | FreeBSD-src-4130080e12ab49a659e616322a16e9db22726595.zip FreeBSD-src-4130080e12ab49a659e616322a16e9db22726595.tar.gz |
It was noticed that we do not change a file's access time when it gets
executed. This appears to violate most of the UNIX-ish standards.
One example quote from:
http://www.opengroup.org/onlinepubs/009695399/functions/exec.html
Upon successful completion, the exec functions shall mark for update
the st_atime field of the file. If an exec function failed but was
able to locate the process image file, whether the st_atime field is
marked for update is unspecified. Should the exec function succeed,
the process image file shall be considered to have been opened with
open().
This appears to take care of it for ufs filesystems, doing the necessary
sanity checks (read-only filesystem, etc) without violating any other
standards (setting atime for any open appears to be allowed in any standards
I could find).
Noticed by: cperciva
Reviewed by: kan, rwatson
Diffstat (limited to 'usr.bin/kdump')
0 files changed, 0 insertions, 0 deletions