OT: Linux tip
Fairlight
fairlite at fairlite.com
Thu Oct 18 11:02:50 PDT 2007
Only Jay Ashworth would say something like:
> I figured out where it was by going to /proc/PID/cwd, and that
> suggested to me, just now, a pretty cool way to tell what's *really*
> running on your machine, assuming someone hasn't monkeyed with ls and
> /proc:
>
> ls -l /proc/*/exe
What can be -really- telling sometimes is what files something has open:
ls -l /proc/*/fd/*
The odd location of your problem file is precisely why when I do audits,
I generate a list of every file on the system that isn't owned by an
rpm (rpm's I audit separately and differently) and go through them all.
Sometimes this is dozens to hundreds of megs long, depending how much data
is on the system. But when you've seen things buried in odd locations like
the /usr/share/locale heirarchy, etc., where nobody would normally look, it
pays to be thorough.
mark->
--
Most people think the defining traits of human beings are intelligence,
speech, writing, or creativity. The sad reality is that the most singular
defining quality of humanity is cruelty. No other species appears to be so
able and willing to inflict pain on its brethren for no logical reason.
More information about the Filepro-list
mailing list