From: Bryan Donlan <bdonlan@gmail.com>
To: Daniel Poelzleithner <poelzi@poelzi.org>
Cc: linux-kernel@vger.kernel.org, Simon Horman <horms@verge.net.au>,
Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
Subject: Re: Suggestion: xtime as new inode attribute
Date: Thu, 17 Dec 2009 02:06:15 -0500 [thread overview]
Message-ID: <3e8340490912162306m4236569s4e497ad01409c756@mail.gmail.com> (raw)
In-Reply-To: <4B292D9A.5060501@poelzi.org>
On Wed, Dec 16, 2009 at 1:57 PM, Daniel Poelzleithner <poelzi@poelzi.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> I would like to suggest a new attribute for inodes in linux filesystems
> to record the last execution time of files.
>
> The problem:
>
> If a linux installation gets older and older, more and more programs get
> installed over time. Mostly to just test them for a particular problem
> and often the deinstallation is forgotten. To find out which packages
> are not used for a long time is currently quite impossible. The user may
> use program X which will run but not depend on program Y as a subprocess
> for example.
>
> The solution:
>
> I suggest a new inode attribute called xtime, which is like atime, but
> will only be updated when a file is executed. This would allow tracking
> of unused binaries and could be used with some clever algorithms in the
> cleanup program to find unused packages for removal or other cleanup
> purposes.
> It would also add an additional information in forensic analysis of
> hacked systems btw.
Why isn't atime sufficient? atime is updated when programs are
executed, and it's uncommon for executable files to be accessed
without being executed; for the purposes of determining whether a
program is needed, it ought to be good enough.
Note that many modern distros use relatime to reduce the (significant)
overhead of atime; this may account for why you may not be seeing
atime update for executables; try mounting with -o strictatime if you
want to see it at work, but beware, as this will bring with it a major
performance hit - which your proposal would as well :)
next prev parent reply other threads:[~2009-12-17 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 18:57 Daniel Poelzleithner
2009-12-17 1:00 ` Simon Horman
2009-12-17 5:47 ` Jeffrey Hundstad
2009-12-18 9:27 ` Daniel Poelzleithner
2009-12-18 14:59 ` tytso
2009-12-17 7:06 ` Bryan Donlan [this message]
2009-12-18 9:19 ` Daniel Poelzleithner
2009-12-19 0:19 ` Junio C Hamano
2009-12-19 1:48 ` Frans Pop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e8340490912162306m4236569s4e497ad01409c756@mail.gmail.com \
--to=bdonlan@gmail.com \
--cc=horms@verge.net.au \
--cc=jeffrey.hundstad@mnsu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=poelzi@poelzi.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®