Hi, On Mon, 10 Dec 2007, Carl Olof Englund wrote:
> And here the output of the command: (ps faux | grep -B 5 "nautilus ") > before logout: > henri 15707 0.0 0.0 33548 252 ? Ss 09:40 0:00 \_ > /usr/bin/ssh-agent x-session-manager > henri 15721 0.0 0.0 3908 468 ? S 09:40 0:00 \_ > /bin/sh /usr/bin/compiz --sm-client-id default0 > henri 15819 0.0 1.9 155280 10188 ? S 09:40 0:00 | > \_ /usr/bin/gtk-window-decorator --replace > henri 15820 0.1 1.6 190488 8676 ? S 09:40 0:03 | > \_ /usr/bin/compiz.real --ignore-desktop-hints --replace --indirect-rendering > --sm-client-id default0 ccp > henri 15724 0.1 3.1 293068 15984 ? S 09:40 0:03 \_ > gnome-panel --sm-client-id default1 > henri 15725 0.0 1.0 220888 5372 ? S 09:40 0:00 \_ > nautilus --no-default-window --sm-client-id default2 > henri 13461 56.6 6.4 354672 32928 ? R 08:43 56:22 nautilus > --no-default-window --sm-client-id default2 So before logout, he had two nautilus sessions. One is attached to this session (started at 09:40), the other is detached (started at 08:43). The detached process has used 56 minutes of cpu time, so I presume it is the problem one. > After logout: > > henri 13461 57.0 6.4 354804 33172 ? R 08:43 57:29 nautilus > --no-default-window --sm-client-id default2 > henri 13472 0.0 0.5 80248 2728 ? Ssl 08:43 0:00 > /usr/lib/bonobo-activation/bonobo-activation-server --ac-activate > --ior-output-fd=16 After logout, you can still see the detached one, so I'd guess you still had the 100% cpu problem. My guess is that the 08:43 session exited uncleanly, nautilus was left running and has ended up consuming lots of cpu doing something strange. There are also one or two other processes left (eg the bonobo-activation-server above). It might be interesting to ask the user "henri" what happened to his 08:43 session, ie did he logout as usual, or did something else happen. As Frederik suggested, the gnome_watchdog script can be installed and goes around routinely killing old dead processes like this. It would be a lot nicer to fix the problem so that these orphaned processes go away of their own accord but that's probably quite involved. I wonder would it be sensible for ldm2 have an extra command or two on the end of its ssh session to kill off processes which linger? Gavin -- edubuntu-users mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
