headers
Lars Tunkrans | 2 May 2003 09:52

FAM-2.6.10 on SPARC/Solaris 9

Hello

I have identified three problems which needs to be fixed
If it is going to be possible to ever use FAM on a SUN
Workstation.

1)  location of mntent.h

     As Rolf Sponsel has reported earlier:

     mntent.h  is in /usr/include/sys/mntent.h
     on Solaris 7/8/9

2)  Declaration for unsigned integrals.

     In several places in the source  " u_int32_t "
     is used.

     Solaris uses the other style  " uint32_t "

     It is arguable that *NIX  operatingsystem should
     be able to handle both as FreeBSD  does.
     Hovewver the /usr/inlclude/sys/types.h  in solaris
     does not include the former style, only the latter of
     these above.

3)  The string "sun"  is a reserved word.

     in  ./libfam/Client.c++
(Continue reading)

Permalink | Reply | 0 comments |
headers
Chris | 3 May 2003 01:06

Compile error on OSX Jaguar

Hello,

I'm trying to compile FAM 2.6.10 on OS X 10.2.5 (gcc version 3.1 
20020420).
For that i applied the freeBSD patch.

the ./configure seems works well (without running autoconf).
but i have errors with make :

any idea ?

Thx a lot.
C.

---- output ---

% make
cd . && aclocal-1.6
cd . && \
   automake-1.6 --gnu  Makefile
cd . && autoconf
/bin/sh ./config.status --recheck
running /bin/sh ./configure   --no-create --no-recursion
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/Users/kubernan/Desktop/fam-2.6.10/missing: Unknown `--run' option
Try `/Users/kubernan/Desktop/fam-2.6.10/missing --help' for more 
information
configure: WARNING: `missing' script is too old or missing
checking for mawk... no
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joel Baxter | 19 May 2003 00:56

fam error "failed to accept new client"

I'm trying to get fam working on a RedHat 7.1 box (x86).  In the 
messages log I'm seeing this:

fam[10247]: failed to accept new client: Invalid argument

I've experimented with using the RedHat-target source RPMs for fam 
2.6.4, 2.6.7, and 2.6.8.  There were no problems with the 
configure/compilation/installation as far as I can tell.  I've tried 
running both the fam test app as well as the post-compile tests for 
Courier IMAP (which uses fam, and is the reason I'm trying to get fam 
installed).  In all cases, when I try to run the app, the above error 
message is generated in the log, and the app fails to work as expected.

chkconfig shows the fam service to be "on", and rpcinfo -p gives me:

    program vers proto   port
     100000    2   tcp    111  portmapper
     100000    2   udp    111  portmapper
     100024    1   udp   1024  status
     100024    1   tcp   1024  status
     391002    2   tcp   1129  sgi_fam

So... on the surface this looks copacetic, but obviously something is 
not working.  Any solution, or just a hint as where to start looking, 
would be appreciated.
Permalink | Reply | 4 comments |
headers
Joel Baxter | 19 May 2003 01:50

Re: fam error "failed to accept new client"

Joel Baxter wrote:
> I'm trying to get fam working on a RedHat 7.1 box (x86).  In the 
> messages log I'm seeing this:
> 
> fam[10247]: failed to accept new client: Invalid argument

Well... fixed.  I updated my xinetd version, and also tried the RedHat 
7.2 binary RPM for fam 2.6.4 rather than compiling it myself.  The 
Courier IMAP post-compile tests now run successfully.

Not sure which of the two changes was key, but don't really care at the 
moment. :-)

If someone knows specifically why I was getting that error message, I'd 
still be interested in hearing it, but it's no longer a blocker.  Also, 
if there's some nasty known problem with 2.6.4, please tell.
Permalink | Reply | 3 comments |
headers
Michael Wardle | 19 May 2003 02:36

Re: fam error "failed to accept new client"

On Monday 19 May 2003 09:50, Joel Baxter wrote:
> Joel Baxter wrote:
> > I'm trying to get fam working on a RedHat 7.1 box (x86).  In the
> > messages log I'm seeing this:
> >
> > fam[10247]: failed to accept new client: Invalid argument
>
> Well... fixed.  I updated my xinetd version, and also tried the RedHat
> 7.2 binary RPM for fam 2.6.4 rather than compiling it myself.  The
> Courier IMAP post-compile tests now run successfully.
>
> Not sure which of the two changes was key, but don't really care at the
> moment. :-)

If my memory serves me correctly, there was an issue with xinetd handling RPC 
version 1 connections for FAM.  I think Alex Larsson (the Red Hat FAM 
maintainer) made a change to the FAM service definition in 
/etc/xinetd.d/sgi_fam to make it only use RPC version 2.  It could also be 
that upgrading to a later version of xinetd fixed the problem in xinetd.  You 
might like to look at the respective changelogs for more details
(example: rpm --query --changelog fam).

> If someone knows specifically why I was getting that error message, I'd
> still be interested in hearing it, but it's no longer a blocker.  Also,
> if there's some nasty known problem with 2.6.4, please tell.

Users were able to monitor files that belonged to the group the FAM daemon was 
running as (group nobody by default on Red Hat Linux).  It's not a huge 
issue, but one you should be aware of nonetheless.  There were also issues 
when monitoring several thousand files that have only recently been fixed
(Continue reading)

Permalink | Reply | 2 comments |
headers
Joel Baxter | 19 May 2003 03:56

Re: fam error "failed to accept new client"

Thanks for the response.  Just to finish this off: it was indeed the 
xinetd version that was the culprit.  I now have FAM running OK as built 
from the 2.6.7 source RPM.

In fact using the binary RPM turned out to be a problem of a different 
sort.  None of the RedHat binary RPMs for FAM include the static library 
libfam.a, and at least one of the many configure scripts in the Courier 
IMAP build actually checks for the existence of libfam.a at one point, 
as part of a does-FAM-exist sequence.  (Even though, as far as I can 
tell, only the dynamic library is actually used by the compile end 
products.)  So that wasn't good.  Rather than hacking at the config 
scripts to make them get the correct answer, I thought I'd try going 
back to the source builds, so that libfam.a would exist, and all seems 
to be well.
Permalink | Reply | 1 comment |
headers
Michael Wardle | 19 May 2003 04:59

Re: fam error "failed to accept new client"

On Monday 19 May 2003 11:56, Joel Baxter wrote:
> Thanks for the response.

Not a problem.

> I now have FAM running OK as built from the 2.6.7 source RPM.

Good.

> In fact using the binary RPM turned out to be a problem of a different
> sort.  None of the RedHat binary RPMs for FAM include the static library
> libfam.a

I suspect this file is in the "fam-devel" package.

--

-- 
Michael Wardle
Adacel Technologies
Permalink | Reply | 0 comments |
headers
Frank Hemer | 22 May 2003 12:12

test

test
Permalink | Reply | 0 comments |
headers
Frank Hemer | 22 May 2003 19:38

Mail delivery failed: returning message to sender

Hi,

I just recently have added fam support to LinCVS (http://www.lincvs.org), a 
graphical frontend for cvs. Implementing this, I encountered problems with 
fam registering many (I tested with about 1200) dirs. The result in many 
cases is a crash. Still, for up to 200 dirs, fam works fine. This seems to be 
a problem with the polling mode, on my test system (SuSE 8.2) fam runs with 
fileschanged, obviously no IMon support.

To fix this, I didn't want to patch my kernel, so I have written a kernel 
module (http://www.fwatch.org) that notifies about change-events, but without 
the need to recompile the kernel.
I have added two files from the fam project, to be able to include this module 
into fam.
I wonder whether anybody is interested to include fwatch-support into fam? The 
contrib files at the moment are just a hack since I was to lazy to change the 
autoconf setup. So it will only properly compile if IMon is not installed on 
the target system.

Keep up the good work,
Regards
Frank
Permalink | Reply | 0 comments |
headers
Michael Wardle | 23 May 2003 02:57

Re: FAM addon/patch

Hello Frank

On Thursday 22 May 2003 22:11, Frank Hemer wrote:
> I tried to post this to the mailing-list, but unfortunatelly, it didn't
> appear. So I'll try direct ...

As you might have noticed, your message has since appeared on the mailing 
list, albeit with the subject "Mail delivery failed: returning message to 
sender".

> I'm core developer of a cvs frontend (http://www.lincvs.org), and have just
> recently included fam support.

Nice to hear.

> When using fam, I realized the FamNextEvent routine throwing errors and
> crashing when monitoring more than at about 200 directories.

I've heard about such a problem before, but haven't made the time to 
investigate why it is occuring.  It's definitely a problem I'd like to fix 
soon, so any input is most welcome.

> It appeared to me, that fam (or fileschanged/dnotify???) was eating up a
> lot of fd's.

Yes, unfortunately this is the way that DNotify works, and FAM on most 
GNU/Linux distributions uses DNotify.

> So finally I decided to write my own kernel notifier, and patch it into
> fam. I built it as a kernel module (linux;-), that hooks into the
(Continue reading)

Permalink | Reply | 1 comment |

Gmane