Re: deb_checkmd5sum?
Since "deb_checkmd5sum" is a running process.
there's better way to locate it on your hard drive.
look into /proc/$PID/exe, which is a link to the full path of the
respective process.
in your case, deb_checkmd5sum caused the system to crash.
so it's possible that you don't have enough time to do this by hand.
write a script that runs just before the cron job to reveal the real
command invoked.
what's more, the file is also very likely to be located with a simple
$ mlocate/locate deb_checkmd5sum
and as mentioned by Jon, a de-prioritized
$ find / -name deb_checkmd5sum
doesn't take up much resource, either.
it dosn't hurt to use mlocate and find in the first place.
Regards,
Tao
--
Link: http://www.google.com/profiles/UniIsland
On Tue, Jun 15, 2010 at 10:49 PM, Miles Fidelman
<mfidelman@meetinghouse.net> wrote:
> For educational purposes only:
>
> That's just a silly suggestion, beyond the obvious of searching for files
> named deb_checkmd5sum, of which there are none - doing a full text search on
> a terabyte of files is just too resource intensive.
>
> In any case, it turns out to be a procedure call inside Tiger - a somewhat
> aging security audit package. Turns out that Tiger runs an hourly cron job
> that, in turn, calls its own routine that parcels out tasks across different
> hours in the day. Buried way deep in nested config files (cron ->
> run.hourly -> tigercron) is a job that runs at 1am that invokes a Tiger
> sub-package called "check_system" - which in turns runs a procedure called
> "checkmd5sum" - which shows up in a process listing as deb_checkmd5sum
> (which, I think, comes from a library). We'll see if turning off that job
> stops the nightly crashes.
>
> I really can't believe there aren't better crash logging facilities for
> Debian.
>
> Huang, Tao wrote:
>>
>> Why not search for the process name in your hard drive?
>>
>> Tao
>> --
>> Link: http://www.google.com/profiles/UniIsland
>>
>>
>>
>> On Mon, Jun 14, 2010 at 7:52 PM, Miles Fidelman
>> <mfidelman@meetinghouse.net> wrote:
>>
>>>
>>> Anybody recognize this process name?
>>>
>>> I'm seeing a nightly crash, and this seems to be running at the time
>>> (I've
>>> been leaving top running in a window - deb_checkmd5sum seems to be at the
>>> top of the list each time the machine crashes).
>>>
>>> I expect it's part of a nightly cron job, but I'm (not yet) sure which
>>> one.
>>>
>>> Thanks for any pointers.
>>>
>>> Miles Fidelman
>>>
>>> --
>>> In theory, there is no difference between theory and practice.
>>> In<fnord> practice, there is. .... Yogi Berra
>>>
>>>
>>>
>>> --
>>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a
>>> subject
>>> of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>>> Archive: [🔎] 4C1617F2.6050803@meetinghouse.net">http://lists.debian.org/[🔎] 4C1617F2.6050803@meetinghouse.net
>>>
>>>
>>>
>
>
> --
> In theory, there is no difference between theory and practice.
> In<fnord> practice, there is. .... Yogi Berra
>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject
> of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] 4C1792FC.3010000@meetinghouse.net">http://lists.debian.org/[🔎] 4C1792FC.3010000@meetinghouse.net
>
>
Reply to: