Hi, From time to time with no pattern I can discern, I'll find an instance of "fam" running consuming as much CPU as it can get. It bears my UID but can only be killed by root. Does anyone know why this happens and / or how to prevent it? Thanks. Randall Schulz
On Monday 18 July 2005 7:59 am, Randall R Schulz wrote:
Hi,
From time to time with no pattern I can discern, I'll find an instance of "fam" running consuming as much CPU as it can get. It bears my UID but can only be killed by root.
Does anyone know why this happens and / or how to prevent it?
Are you running beagle? I seem to remember that beagle uses fam to detect changes that it needs to index. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-21.7-default x86_64 SuSE Linux 9.3 (x86-64)
Scott, On Monday 18 July 2005 19:30, Scott Leighton wrote:
On Monday 18 July 2005 7:59 am, Randall R Schulz wrote:
Hi,
From time to time with no pattern I can discern, I'll find an instance of "fam" running consuming as much CPU as it can get. It bears my UID but can only be killed by root.
Does anyone know why this happens and / or how to prevent it?
Are you running beagle? I seem to remember that beagle uses fam to detect changes that it needs to index.
No. Both beagle and Kat are classified "not ready for prime time" for me.
Scott
Randall Schulz
On Monday 18 July 2005 9:56 pm, Randall R Schulz wrote:
Scott,
On Monday 18 July 2005 19:30, Scott Leighton wrote:
On Monday 18 July 2005 7:59 am, Randall R Schulz wrote:
Hi,
From time to time with no pattern I can discern, I'll find an instance of "fam" running consuming as much CPU as it can get. It bears my UID but can only be killed by root.
Does anyone know why this happens and / or how to prevent it?
Are you running beagle? I seem to remember that beagle uses fam to detect changes that it needs to index.
No. Both beagle and Kat are classified "not ready for prime time" for me.
Oh well, it was just a thought. A little googling reveals that you are not the only one with this symptom.... I noted several comments regarding this happening when moving large files, or working with mounted remote file systems without portmap running. Google groups had some interesting posts, use search term 'linux fam 100% cpu' Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-21.7-default x86_64 SuSE Linux 9.3 (x86-64)
On Mon, 2005-07-18 at 07:59 -0700, Randall R Schulz wrote:
From time to time with no pattern I can discern, I'll find an instance of "fam" running consuming as much CPU as it can get. It bears my UID but can only be killed by root. This is the file alteration monitoring (or something like that) daemon.
Does anyone know why this happens and / or how to prevent it? rcfam stop
I have searched high and low for the rationale behind this, and why it goes bonkers every now and again, and the only sensible use I've read about is when running imap servers, if you're allowing multiple logins to the same account. What annoys me to no end, is that courier fills your mail log with thousands of error messages if fam isn't running, and I haven't been able to force courier *not* *to* *log* - I don't need it to log in most of my installations. -- Kind regards Hans du Plooy SagacIT (Pty) Ltd hansdp at sagacit dot com
participants (3)
-
Hans du Plooy -
Randall R Schulz -
Scott Leighton