Re: famd hogs all CPU time
On Tuesday 30 August 2005 15:17, Greg Folkert wrote:
> 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.
Well, I admit I wasn't too sure of what it did, but I read the description and
what you said is what I imagined it did, so I went ahead and restarted it, as
my machine doesn't serve anything and I wasn't running any programs in which
it could cause trouble that I could think of.
That's why I said to be careful on mission-critical systems. I was just
talking about my experience on a workstation serving nothing at all and no
files being accessed by more than one program at a time, which is probably
not much help anyway. It was just my 2 cents.
But now the question arises: should such a system be running famd? Is it
necessary when you're not running a server?
--
~vi
Reply to: