This problem should have been resolved by our update to SL4.8.

Occasionally the gam_server (the Gnome File Alteration Monitor) process enters a loop and starts eating CPU.

In general, it is safe to just kill gam_server. It will then be started automatically when needed. Adding the following to ~/.gaminrc may help prevent it from looping and using up CPU (once gam_server has been restarted).
notify /*
fsset nfs none
fsset afs kernel 100
fsset ext3 kernel 100
fsset vfat none

For more information, please see the following links.

This topic: Computing > WebHome > LinuxSupport > GamServer
Topic revision: 20 Apr 2010, dab66
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding CLASSE Wiki? Send feedback