gam_server?

andyholland · 08-17-2007, 12:23 PM

Thanks for the post about gaminrc in /etc. I believe it is working.

andy holland

andyholland · 10-16-2007, 01:28 PM

Quote:

Originally Posted by deesto

Since it is not malicious code, I wouldn't call it a "virus," but its out-of-control nature does lend itself to the possibility of bad coding. It seems to be a harmless package that tries to do good things (tracking file changes for you is a good thing), but there's got to be a better way of keeping it under control than waiting for it to consume 100% CPU so it can be killed.

I also wonder whether this gam_server CPU cycle problem has something to do with my files/folders not being updated in Nautilus until I manually refresh?

Harmless? I tried the solution below - it seemed to work for awhile, now it doesn't!

I have a 4 CPU system. When two people are on it, and gam_server magically decides to use 2 CPUs, guess what happens? Its been going on for nearly a year.

Its a very serious thing to write a piece of software that uses all sorts of resources and won't die. It may not have been malicious, but that doesn't make it "harmless."

This computer is used for cancer research and wasting time monitering the system to assure that gam_server is not running amok is not a good use of time.

wolfperkins · 10-30-2007, 11:06 AM

Quote:

Originally Posted by gpayne

I put the gaminrc file directly in the /etc directory and it worked like a charm (after I sent a "kill -1" to the gam_server pid).

I am using RHEL 4 and did just that and it worked for me too.

Thanks a lot!

deesto · 05-27-2008, 02:06 PM

Quote:

Originally Posted by wolfperkins

I am using RHEL 4 and did just that and it worked for me too.
Thanks a lot!

Belated thanks for me as well; I decided to tolerate this problem for as long as my patience would hold, which lasted until just now. Adding a line to (a new) /etc/gaminrc file, along with a 'kill -1' afterward, seem to have worked for me was well on RHEL4.

deesto · 06-18-2008, 05:20 PM

Quote:

Originally Posted by deesto

Belated thanks for me as well; I decided to tolerate this problem for as long as my patience would hold, which lasted until just now. Adding a line to (a new) /etc/gaminrc file, along with a 'kill -1' afterward, seem to have worked for me was well on RHEL4.

Looks like I have to retract my previous statement! Guess who came back for a visit:

Code:

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
20139 jd        25   0  2728 1316  876 R  100  0.1  20713:15 gam_server

I've watched top for about an hour now, and this hasn't changed.