Huang, Tao wrote:
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
which assumes that I'm running locate, which I'm not.
and as mentioned by Jon, a de-prioritized
$ find / -name deb_checkmd5sum
which, as noted in my previous message would have yielded absolutely
nothing - it turns out to be a procedure name within another piece of code
--
In theory, there is no difference between theory and practice.
In<fnord> practice, there is. .... Yogi Berra
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c17a940.2060...@meetinghouse.net
