Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uunet!overload!dillon From: dillon@overload.Berkeley.CA.US (Matthew Dillon) Newsgroups: comp.sys.amiga.programmer Subject: Re: Watching a dir Message-ID: Date: 2 May 91 20:47:03 GMT Article-I.D.: overload.dillon.7195 References: <1991May1.170440.13999@jato.jpl.nasa.gov> Organization: Not an Organization Lines: 34 In article <1991May1.170440.13999@jato.jpl.nasa.gov> jdickson@jato.jpl.nasa.gov (Jeff Dickson) writes: > > Since there has much talk of AmigaDOS 2.0, let me hit you all with >this. > >assumptions correct? UNIX filesystem maintains a date stamp that is updated >everytime a file is accessed. AmigaDOS does not. So if there was some way >to tell what file had been accessed - there would be no way to determine >directly from the filesystem the frequency. The program would have to main- >tain its own datestamp database. > > I'm trying to see the light at the end of the tunnel on this. Anyone >else have any input on this? > > thanks, Jeff UNIX has a last-access-time field, AmigaDOS does not. The only two things in UNIX that really uses the atime field are: (1) the shell to determine when to print the 'you have new mail' message. (2) system auto-compress programs that compress old unused files (for systems that don't have much disk space) Frankly, I don't see much of a need for it. It would generate too much disk traffic under AmigaDOS. -Matt -- Matthew Dillon dillon@Overload.Berkeley.CA.US 891 Regal Rd. uunet.uu.net!overload!dillon Berkeley, Ca. 94708 USA