[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: famd hogs all CPU time



On Tue, 2005-08-30 at 14:39 -0500, Vi Arguelles wrote:
> On Tuesday 30 August 2005 05:46, Saverio Trioni wrote:
> >
> > Hi. I have the same problem. I don't dare to kill famd but it runs as
> > my user. I think it should run as root...

Saverio, if it ran as root for managing your stuff... hmm that would be
giving too much privilege. If it runs as your user (typically only
touching your stuff) then it should not be able to be hijacked, even if
so it would only be your stuff.

Running as root, the initial daemon does, but drop privilege when
spawned for a user.

> Mmm, I did it once. I didn't kill it kill it. I just restarted the daemon and 
> all was well. I had no problems, but YMMV. If you're not on a 
> mission-critical system, you might as well try it.

Vi, even then it might just not be noticed. I am thinking that you are
not clear as to what FAMD just is.

-------------------
Description: File Alteration Monitor
 FAM monitors files and directories, notifying interested applications
 of changes.

 This package provides a server that can monitor a given list of files
 and notify applications through a socket. If the kernel supports dnotify
 (kernels >= 2.4.x) FAM is notified directly by the kernel. Otherwise it has
 to poll the files' status. FAM can also provide a RPC service for monitoring
 remote files (such as on a mounted NFS filesystem).
--------------------

So you see, it is a monitoring device, so things like multiple IMAP
client can access the same mailbox at once and all will show it. It is
just a matter of not stepping on toes, is what FAMD does.

-- 
greg, greg@gregfolkert.net

The technology that is 
Stronger, Better, Faster: Linux

Use Debian GNU/Linux, its a bazaar thing.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: