According to gnome-system-monitor (by checking the dependencies option) this 
"nameless" process has no parent, just like "init".
I'm not even sure whether this is possible, but something must be wrong if 
system-monitor can't figure out it's parent. I would look in proc for details, 
but the process dies too quickly.

I've noticed this problem after making some configuration changes in
syslog-ng (to execute sshguard when a break-in attempt is logged).

-- 
Process with no name
https://bugs.launchpad.net/bugs/606710
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to