Summary: | FAM (famd) starts using 100% of CPU | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jure Repinc <jlp.bugs> |
Component: | Current packages | Assignee: | foser (RETIRED) <foser> |
Status: | RESOLVED UPSTREAM | ||
Severity: | major | CC: | iyosifov, marc |
Priority: | Low | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://forums.gentoo.org/viewtopic.php?t=257289 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jure Repinc
2004-12-24 03:41:34 UTC
This is also happenening to me at least once a day. Everytime my computer (AMD64) slows down.. I look over and famd is using 100% again. Although I do not use Krusader, the time that this happens to me most is using Konqueror while browsing an nfs drive. I will click on a file or move a file and it just causes an overload in famd. Any information needed, I will gladly provide. this is not amd64 specific, happened to me on various machines (x86 and amd64), I stopped using famd for that reason try gamin.. fam is coming to an end. Yes, gamin looks good, but as far as I can tell, there are no stable builds for ANY arch for gamin.. that seems a little too early to jump in for me. Since it is a mature prog, fam(d) should be stable, and certainly be more stable than it is if it is marked as such in the portage tree. Something that crashes daily for a LOT of people (see forums for many topics on this) should be worked out, or fam should be marked as '~' , IMO of course. well investigate it then, be my guest. I've not used fam itself for quite some time, but I do know it's main problem is it using dnotify & locking, not 100% cpu usage as you report. I bet thats a problem origination somewhere else : app, kernel, etc. Found some info here: http://oss.sgi.com/bugzilla/show_bug.cgi?id=158 http://oss.sgi.com/projects/fam/mail_archive/200301/msg00011.html Don't know if this helps but this bug is getting annoying. i have the same problem here on x86-32 (P4). It happens 2-3 times a month, and I have to restart famd... Happening dayly here too (x86 Athlon-XP). Googleing show this happening for other dists too. Will shut down this PITA software and try my lucks with Gamin instead. Perhaps time to make a Gamin not ~arch if it actually works and drop FAMD in general? Havening the same problem here on a Athlon-XP. Any news about how to solve this? Is it possible to log some output of famd? Does anyone know about that? >>> Any news about how to solve this?
Try gamin.
"Try gamin." is an stupid answer to this bug, isn't it? (In reply to comment #11) > "Try gamin." > > is an stupid answer to this bug, isn't it? If you have better advice for the people experiencing this problem, please share it with us. (In reply to comment #12) > If you have better advice for the people experiencing this problem, > please share it with us. Well, first, experience the overheating issues on a server with famd, and then, suggest us for a production server to emerge a masked package again... doesn't it sucks? I don't have better advice, only suggestions... And I will shut up them. Thank you very much for nothing at all. upstream problem, bug already exists. The only realistic solution is the one in comment #3 & #10; there just is zero progress on FAM, go with gamin. The ~arch-ness of gamin has to do with the inotify backend API changes over time, the newest version (0.1.2) is the most likely candidate to be stabilized pretty soon now inotify has landed in the kernel. The other backends should do just fine if you do not have inotify. |