I took the "bind" entry out as suggested, and it doesn't seem to help.
I don't think that setting should matter anyway, as we're not trying to
use FAM on a non-local machine. The only thing running on a non-local
machine is the NFS server. Here's a bad diagram:
MACHINE A
FAM Client Running
FAM Server Running
Watching /mnt/nfs/somedir-->NFS---->/somedir/somefile
NFS Server
MACHINE B
From Machine A, "touch /mnt/nfs/somedir/somefile" is picked up by FAM.
When you do "touch /somedir/somefile" from Machine B, nothing happens.
I've been wondering if this is the same problem described in FAM bug
#166 ("Pollster broken by DNotify patch",
http://oss.sgi.com/bugzilla/show_bug.cgi?id=166). Looking at the RH
source, it does seem to have the DNotify patch. The code referenced in
comment #2 is not the same as the code in the patched RH source, though,
and I can't really tell if this bug was addressed in their code or not.
I'm not even sure which version of FAM the bug report would apply to.
Does anyone know about this, or have some suggestions? Thanks!
Michael Wardle wrote:
On Sat, 2003-04-12 at 02:55, Ken Tanzer wrote:
We're trying to use FAM to monitor files on a directory that is mounted
via NFS.
This works fine when a file is modified via the local machine on which
FAM is running. When the file is changed from the server that is
exporting NFS, however, FAM does not detect this, and does nothing.
By default, Red Hat ships with the FAM daemon bound to the loopback
interface so that it can only be used by the local machine.
Try removing the "bind = 127.0.0.1" entry in /etc/xinetd.d/sgi_fam.
|