Florian Bachmann wrote:
1)
What is the current status of imon? Will it be maintained for upcoming
kernel releases, are there alternatives, etc.
I believe I have answered this question a few times here, and it's also
partially mentioned in the FAQ. You may want to read back thru the
mailing list
http://oss.sgi.com/projects/fam/mail.html
and the FAQ
http://oss.sgi.com/projects/fam/faq.html
to see full answers to these questions.
Here's a few URLs that might help you:
http://oss.sgi.com/projects/fam/faq.html#what_os_imon
http://oss.sgi.com/projects/fam/archive/msg00394.html
http://oss.sgi.com/projects/fam/archive/msg00424.html
To answer your question briefly:
IMon is still alive, but I'm not maintaining it. DNotify is an
alternative that's now available in official Linux kernels, so that is
what I'd recommend using.
I'll soon merge Alex Larsson's DNotify patch into our tree, but until
then, you can get the DNotify patch from:
ftp://oss.sgi.com/projects/fam/download/contrib/dnotify.patch
As usual, get a copy of the FAM distribution (sources), extract the
files, and run "patch -p1 < /path/to/dnotify.patch" to apply the patch.
2)
Are there any reliable statistics on how many monitored files/directories FAM
can handle at a time (both local and networked filesystems)? Is it really
feasible to use FAM on some hundreds of files at a time, or should I just
forget about that?
I think there is a limitation meaning that no more than 1024 files can
be monitored simultaneously, but this may be a limitation of the kernel
monitor (such as IMon) rather than a limitation of FAM. I would
appreciate if somebody could provide a more definitive answer.
3)
From the INSTALL file in the distribution archive: "The install target doesn't
modify your configuration files; you'll have to do this yourself". Yet, after
running make install I found that /etc/rpc and /etc/inetd.conf had been
modified. Hmmm.... I may be paranoid but this gives me a bad feeling.
The statement in INSTALL is incorrect. The former maintainer (Rusty)
did some work with something called "editconf" that manipulated the
necessary files to make FAM work thru inetd. Provided that your
configuration files were modified in accordance with the instructions in
INSTALL, then there's little need to worry that your version was modified.
I'm planning on removing the existing "make install" target and
replacing it with something simpler, but there's a few people at SGI
that still need the target as it is.
This topic is also mentioned in the FAM FAQ, but I apologize for the
inconsistency.
--
MICHAEL WARDLE
SGI Desktop & Admin Software
Adacel Technologies Limited
--
Source code, list archive, and docs: http://oss.sgi.com/projects/fam/
To unsubscribe: echo unsubscribe fam | mail majordomo@xxxxxxxxxxx
|