Arch Linux

Llama

Banned

From: St.-Petersburg, Russia

Registered: 2008-03-03

Posts: 1,379

FAM going berserk

Hi, everybody,

An interaction between the Krusader and FAM (plus transparent archiving, perhaps) sometimes leads to FAM hyperactivity (some bug). The CPU load springs to 100% and stays there indefinitely; KDE System Guard shows that famd is the culprit. What is the cleanest thing to do in such a case? Killing a daemon doesn't seem to be a perfect solution: it's got a job to do, after all .

lucke

Member

From: Poland

Registered: 2004-11-30

Posts: 4,018

Re: FAM going berserk

FAM in KDE is redundant, you can safely disable the daemon.

Last edited by lucke (2008-06-11 08:09:41)

Llama

Banned

From: St.-Petersburg, Russia

Registered: 2008-03-03

Posts: 1,379

Re: FAM going berserk

This

http://wiki.archlinux.org/index.php/Beg … #About_KDE

is out of date, then?

lucke

Member

From: Poland

Registered: 2004-11-30

Posts: 4,018

Re: FAM going berserk

Apparently.

pressh

Developer/TU

From: Netherlands

Registered: 2005-08-14

Posts: 1,719

Re: FAM going berserk

you only need FAM in either gnome or KDE if you want remote filesystem monitoring. For local filesystem monitoring both can use kernel based inotify.

moljac024

Member

From: Serbia

Registered: 2008-01-29

Posts: 2,676

Re: FAM going berserk

So what does amarok use for scanning music directories for new files ?

---

The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner.
--------------------------------------------------------------------------------------------------------------
But if they tell you that I've lost my mind, maybe it's not gone just a little hard to find...