On Friday 04 July 2003 08:55, phriedrich wrote: > On Fri, 4 Jul 2003 08:25:59 -0400 > > Jason Straight <[EMAIL PROTECTED]> wrote: > > Fam runs through xinetd doesn't it? So it wouldn't be running unless > > there were a connection to it. > > Yes...so it is, I solved this problem a bit later...there was a failure in > the fam-configuration of xinetd...i don't know why, but now it is > working... e17 runs now!
What was the problem with the fam config for xinetd? I have been having problems with my system logs getting filled up with stuff like this: Jul 3 22:31:55 visitoth xinetd[26685]: libwrap refused connection to sgi_fam from <no address> Jul 3 22:31:55 visitoth xinetd[26686]: warning: can't get client address: Transport endpoint is not connected Jul 3 22:31:55 visitoth xinetd[26686]: libwrap refused connection to sgi_fam from <no address> Jul 3 22:31:55 visitoth xinetd[26687]: warning: can't get client address: Transport endpoint is not connected Jul 3 22:31:55 visitoth xinetd[26687]: libwrap refused connection to sgi_fam from <no address> Jul 3 22:31:55 visitoth xinetd[1808]: Deactivating service sgi_fam due to excessive incoming connections. Restarting in 30 seconds. Jul 3 22:32:26 visitoth xinetd[1808]: Activating service sgi_fam With hundreds of the "refused connection" messages before each shutdown/ restart of the fam service by xinetd. I have not been able to reproduce the problem on demand as I'm not sure what is triggering the whole mess. This has been bothering me for some time now, but when I bring it up on the list, no one seems interested... :^( -C.S. -- +-% He's a real UNIX Man $-+------------------------------------+ \ Sitting in his UNIX LAN \ Charles A. Shirley \ \ Making all his UNIX plans \ cashirley (at) comcast (dot) net \ +------# For nobody @------+------------------------------------+
