> Anyway, I was referring to the FL_LEASE lock type which went in with
> 2.4.0-test9-pre7 which should allow file watching to occur without the
> imon patch.
I didn't know that went in. Looks like I've got some catching up to do :)
> I feel though, that it should be possible to cause fam calls to fall
> through to direct watches on the local system via lease locks in the case
> where the files are not network-provided.
Sure, under the covers, the fam API should use whatever mechanism is
available.
> Yes, this is the approach I'm taking. Ideally I think it should be
> possible to say ./configure --no-fam . Perhaps I should be the one to
> implement this after I learn automake and friends.
I think the AC_ARG_WITH macro (or possibly the AC_ARG_ENABLE macro) is what
you want; there's a not-particularly-good example of it at the top of rhino's
configure.in, and in its sysadm_base.m4. Based on the value you get from the
command line, I think you'll need to AC_DEFINE some variable like HAVE_FAM
(you'll need to add that to acconfig.h, too) and then actually use it wherever
fam is being used.
I know that once a Makefile has been generated, it will detect some changes to
configure.in etc., but I think you're better off running autoconf && automake
&& rm config.cache && ./configure --whatever yourself after modifying
configure.in, and running autoheader etc. after modifying acconfig.h. (Also
if you want to see what arguments you last ran the configure script with, head
config.status.)
--Rusty
--
Source code, list archive, and docs: http://oss.sgi.com/projects/rhino/
To unsubscribe: echo unsubscribe rhino | mail majordomo@xxxxxxxxxxx
|