gam_server

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.

• http://www.gnome.org/~veillard/gamin/
• https://bugzilla.redhat.com/show_bug.cgi?id=132354
• https://bugzilla.redhat.com/show_bug.cgi?id=244633
• http://www.linuxquestions.org/questions/linux-networking-3/gamserver-234318/