On Mon, 26 Sep 2011 15:17:05 +0200 Micky L Martin
>Already did lsof and process tracing but to no avail. Does anyone
have any idea how to find that culprit process?
Wanting to mitigate the situation by modifying the system is
understandable but not a best practice as you would be removing
"evidence" (if any). I'd first check if it's the usual suspects
like prelink and if that's not the case then set a watch on it
using inotify, Auditd or loggedfs. If that doesn't lead to clues
use a Live CD to check the file system.
* IMO the whole topic is a bit off-topic for this mailing list.
Feel free to open a thread in a Linux forum or on a general purpose
mailing list you frequent (if any). I can usually be found at
Get latest updates about Open Source Projects, Conferences and News.