I've set up an Edubuntu (AMD64 Gutsy) server running here at school, with so
far three clients attached to it. We're having trouble, though, with nautilus
processes (of different users) eating up all the CPU on the server, slowing
things to a crawl.

Sound familiar to anyone? Up til now I've been logging in via SSH
doing "killall nautilus" but it's happening so frequently I don't think it's
an acceptable solution. If I'm not around keeping an eye on things, the
system is close to unusable.

/ Carl

--
"So slay me now! I have little magic left."
- Kallak, leader of the royal mystics

--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users

Hi,

On Tue, 04 Dec 2007, Carl Olof Englund wrote:

> I've set up an Edubuntu (AMD64 Gutsy) server running here at school, with so
> far three clients attached to it. We're having trouble, though, with nautilus
> processes (of different users) eating up all the CPU on the server, slowing
> things to a crawl.
>
> Sound familiar to anyone?

That sounds highly unpleasant. Is there anything in the users'
.xsession-errors files which might indicate what problem nautilus is
having?

As a test, you might try turning off LOCALDEV in lts.conf to see if the
problem goes away.

Gavin


--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users

Hi!I've had similar problems, but they solved when appling the gnome_watchdog-script.
http://www.morokeni.ch/edubuntu/gnome-watchdog_0.9.2_i386.deb
Regards
Fredrik Jansson, Forsmarks skola, SwedenOn Dec 4, 2007 10:39 AM, Carl Olof Englund <
realdiskdoc@gmail.com> wrote:
I've set up an Edubuntu (AMD64 Gutsy) server running here at school, with so

far three clients attached to it. We're having trouble, though, with nautilus
processes (of different users) eating up all the CPU on the server, slowing
things to a crawl.

Sound familiar to anyone? Up til now I've been logging in via SSH

doing "killall nautilus" but it's happening so frequently I don't think it's
an acceptable solution. If I'm not around keeping an eye on things, the
system is close to unusable.


/ Carl

--
"So slay me now! I have little magic left."
- Kallak, leader of the royal mystics

--
edubuntu-users mailing list

edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users



--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users

Hi,

On Tue, 04 Dec 2007, Fredrik Jansson wrote:

> I've had similar problems, but they solved when appling the
> gnome_watchdog-script.
>
> http://www.morokeni.ch/edubuntu/gnome-watchdog_0.9.2_i386.deb

this suggests that nautilus programs are being left running after logout and
are getting confused taking up lots of cpu (either that or you're killing
running users' nautilus sessions).

Could you check this by running:

ps faux | grep -B 5 "nautilus "

This should show you a bunch of 5-line groups like this one:

joannet 15748 0.0 0.0 4224 1540 ? S 11:49 0:00 | \_ /bin/bash --login -c env LTSP_CLIENT="brooks" PULSE_SERVER=tcp:87.42.170.237:4713 ESPEAKER=87.42.170.237:16001 /etc/X11/Xsession && ltspfsmounter all cleanup
joannet 15749 0.0 0.3 30068 10888 ? Sl 11:49 0:00 | \_ x-session-manager
joannet 15780 0.0 0.0 4252 524 ? Ss 11:49 0:00 | \_ /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-session-manager
joannet 15847 0.0 0.1 13080 5644 ? S 11:49 0:00 | \_ /usr/bin/metacity --sm-client-id=default0
joannet 15850 0.5 0.4 39260 14908 ? S 11:49 0:01 | \_ gnome-panel --sm-client-id default1
joannet 15851 0.5 0.5 76264 16524 ? S 11:49 0:00 | \_ nautilus --no-default-window --sm-client-id default2

This tells you that nautilus running as joannet with pid 15851 is a child of
the x-session-manager[15749], which is still also running. If the bad one you
find is not a child of a running x-session-manager, then the chances are that
person is now logged out and nautilus hasn't closed properly.

It would make things more clear to know if the process is a child or not.

Gavin


--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users

Moin!

Am Dienstag, den 04.12.2007, 11:39 +0200 schrieb Carl Olof Englund:
> I've set up an Edubuntu (AMD64 Gutsy) server running here at school, with so
> far three clients attached to it. We're having trouble, though, with nautilus
> processes (of different users) eating up all the CPU on the server, slowing
> things to a crawl.

This seems to be a bug in ubuntu/edubuntu 7.10. On my ubuntu 7.1 pc i
get this problem often after logging out and in again at once. I wrote a
bugreport at https://bugs.launchpad.net/ubuntu/+bug/153180 but did not
worked on the problem any longer, because i don't log out and in so
often. I also can't reproduce the problem if i want to. But it is still
there.

I think your problem is the same and is not special to edubuntu.

Kai Wüstermann


--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users