Xref: utzoo comp.unix.wizards:8699 comp.os.misc:442 comp.os.vms:6284
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!rutgers!mtunx!mtuxo!mtgzy!mtgzz!avr
From: avr@mtgzz.UUCP (XMRP50000[jcm]-a.v.reed)
Newsgroups: comp.unix.wizards,comp.os.misc,comp.os.vms
Subject: Re: Uses for access time
Summary: Which systems update access time on exec
Message-ID: <4084@mtgzz.UUCP>
Date: 10 May 88 14:57:38 GMT
References: <3672@lynx.UUCP> <8726@oberon.USC.EDU> <4876@cup.portal.com> <375@hotlr.ATT>
Distribution: na
Organization: AT&T, Middletown NJ
Lines: 19

In article <2651@ttrdc.UUCP> levy@ttrdc.UUCP (Daniel R. Levy) writes:
> In article <4054@mtgzz.UUCP>, avr@mtgzz.UUCP (XMRP50000[jcm]-a.v.reed) writes:
> > Unfortunately, "access time" is NOT updated when an executable is
> > executed.
> You should qualify your statement with "not ALWAYS updated", unless you specify
> a specific system.  This machine obviously updates access time upon execution:
> Gurus:  Which systems DO update access time upon execution (presuming it's
> possible at all, e.g., not on a readonly filesystem)?  Which systems don't?

Of the systems I'm currently using:

USG 2.0v2p on vax-780 does NOT
Unix PC (hybrid) 3.5 does
BSD 4.2 on Sun 3/60 does
USG 5.2.5 on Amdahl does NOT if the sticky bit is set; does otherwise.

Updating st_atime on exec is NOT required by SVID (Issue 2; Vol.1,
p. 127).
					Adam Reed (mtgzz!avr)