On Wed, Mar 09, 2005 at 07:35:13PM +, Silas S. Brown wrote:
Package: popularity-contest
Version: N/A; reported 2005-03-09
Severity: normal
popularity-contest reports the atime (access time) of files in packages, but
if you mount your disk with noatime option (if you want to reduce the
On Thu, Aug 04, 2005 at 04:58:53PM -0500, Nathan Stratton Treadway wrote:
A related issue is the case where a program such as integrit updates
the atime of all files in /bin and /usr (and elsewhere) each day.
[...]
So, my point is that if you add special handling for the noatime case,
you
A related issue is the case where a program such as integrit updates
the atime of all files in /bin and /usr (and elsewhere) each day.
For example, a popcon submission on one of my systems (a few months ago)
looks like:
POPULARITY-CONTEST-0 TIME:1108386306 ID:[...]
1108386315 1089347334
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
[Nathan Stratton Treadway]
A related issue is the case where a program such as integrit updates
the atime of all files in /bin and /usr (and elsewhere) each day.
Hm, that will really make it hard to detect if a package was really
used the last week, yes. :/
(In addition eventually dealing
Package: popularity-contest
Version: N/A; reported 2005-03-09
Severity: normal
popularity-contest reports the atime (access time) of files in packages, but
if you mount your disk with noatime option (if you want to reduce the number
of disk writes in order to use a solid-state drive or noflushd)
6 matches
Mail list logo
