famd hogging the CPU
Apparently KDE3 and famd (file alteration monitor daemon) don't play
nicely together. There's a bug already filed against famd. famd hogs
the CPU, possilby polling for changes. I'm using Linux 2.4.19 and there
famd is supposed to use the resource-saving dnotify method for
detecting changes. Deinstalling famd, and thereby forcing KDE to do the
polling itself, circumvents the problem.
Does anyone know what and why is happening? How to tell famd to play
nicely?
Michael
--
Michael Schuerig If at first you don't succeed...
mailto:schuerig@acm.org try, try again.
http://www.schuerig.de/michael/ --Jerome Morrow, "Gattaca"
Reply to: