On Thu, Aug 04, 2005 at 04:58:53PM -0500, Nathan Stratton Treadway wrote: > The issue is that all the atime values fall in a short range (e.g. > 1108386315 - 1108384615 = 1700 sec < 30 minutes) and occur just before > the runtime of popularity-contest itself. > > > So, my point is that if you add special handling for the noatime case, > you might want to also handle the "atimes are all too close together" > problem at the same time.
I should have spelled out that the side-effect of this range of atimes is that ALL packages with valid files are considered "recently used"; none of them ever get tagged as OLD (or anything else; they are left untagged). I guess this situation is the exact opposite of that caused by noatime partitions, which cause packages to get marked as OLD even when they are being used. Nathan ---------------------------------------------------------------------------- Nathan Stratton Treadway - [EMAIL PROTECTED] - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]