FAM is the File Access Monitor.

I had a LOT of experience with FAM on SGI Origins 2000s back
in 1997-98.  Basically, it was unreliable at that time in
IRIX because the FAM daemon would "lock" in some kind of weird
loop after some amount of time (which was very variable; it
would work fine for 2 days, or might lock up in 2 minutes).
We ended up abandoning FAM and rolling our own solution; it
wasn't quite as "pretty" and there was a latency involved
that FAM would have avoided, but it worked, while FAM didn't.

FAM was (and is) much improved since then, and SGI took it
to Linux a while back now.

It would be very useful if you need to monitor for changes
to files, in order to do automated processing (what I was
working on; we had automated retrieval of satellite data
and tried to use FAM to help us kick off processing on
the data as it arrived in discrete units).

Bill Ward

> -----Original Message-----
> From: Edward Dekkers [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 23, 2002 9:50 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Speaking of ports
> 
> 
> > Look at /etc/xinetd.conf, and inside /etc/xinetd.d/ to see of of the
> > services has asked xinetd to listen on its behalf on port 1024.
> >
> 
> The only thing I can find that is not disabled bar what I 
> need (I only use
> the ipop3 and pop-3 services in xinetd), is
> 
> sgi_fam
> 
> What is it and could it be responsible for port 1024 being open?
> 
> Regards,
> Ed.
> 
> 
> 
> 
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
> 



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to