Tony Earnshaw wrote:

That's not true... I've run Courier's IMAP server with several different Red Hat releases, and you won't get any errors when FAM is configured properly.

I've seen primarily two different issues discussed on the list. The first is sgi_fam not functioning because one or more of portmap, xinetd, or sgi_fam had been disabled to increase security. The other is that early releases of gamin had an fd leak that would cause it to stop working after it'd been used for a while. This was especially pronounced in virtual hosting setups where all users use the same gamin daemon.

If you're using a Red Hat release that includes the "fam" package, you can tell whether or not it works by using rpcinfo:

# rpcinfo -p localhost program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 32768 nlockmgr 100021 3 udp 32768 nlockmgr 100021 4 udp 32768 nlockmgr 391002 2 tcp 51303 sgi_fam

If rpcinfo doesn't show sgi_fam, then refer back to the message that I sent earlier today, at 8:36am. It contains all of the info you should need to make sure that sgi_fam is available (well, unless you've locked yourself out of portmap, using tcpwrappers).

If you're using a Red Hat release that includes the "gamin" package, make sure it's the latest one available from Red Hat. It doesn't need any supporting daemons to run, it should always work.