21 Feb
2008
21 Feb
'08
15:07
lsof -p PID see where it's located, my best guess would be that it's a perl script forking itself again if you kill it. Find the source file and remove it.
Oddly, that listed nothing. I think it is because stdout is redirected to a file, so that would show up as an open file in he parent: init. No other files are listed in /proc for that process. But I see in /proc that it has (had) over 320 sockets open. -- Roger Oberholtzer </quote> lsof should return same content as it reads from /proc, if it works for other PIDs but not for that one, I'd suspect a root compromise. -- Best regards, Nick Zeljkovic -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org