Xref: utzoo comp.unix.wizards:8323 comp.os.misc:430 comp.os.vms:5966 Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!pasteur!ucbvax!decwrl!hplabs!sdcrdcf!trwrb!aero!venera.isi.edu!raveling From: raveling@vaxa.isi.edu (Paul Raveling) Newsgroups: comp.unix.wizards,comp.os.misc,comp.os.vms Subject: Re: Uses for access time Message-ID: <5439@venera.isi.edu> Date: 6 May 88 16:06:13 GMT References: <3672@lynx.UUCP> <8726@oberon.USC.EDU> <4876@cup.portal.com> <4054@mtgzz.UUCP> <10730@steinmetz.ge.com> Sender: news@venera.isi.edu Reply-To: raveling@vaxa.isi.edu (Paul Raveling) Distribution: na Organization: USC-Information Sciences Institute Lines: 20 In article <10730@steinmetz.ge.com> davidsen@kbsvax.steinmetz.UUCP (William E. Davidsen Jr) 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. I was once on a system whose very clever administrator wrote a >>demon to archive any file not "accessed" in the last month. He soon >>archived an executable I was exec'ing every day from my .profile. > >I tried this on several systems, and it seems that you are correct for >BSD (at least the Ultrix and SunOS versions), but not for SysV (again at >least Xenix and 2B2/300 flavors). I'm glad you pointed this out, since I >do just what you mention on my machine (SysV). Another system: HP-UX (version 5.5) DOES update last-access time on executing a file. --------------------- Paul Raveling Raveling@vaxa.isi.edu