On Thursday 23 January 2003 20:45, Tim Lee wrote:
>gnome-keybinding-properties seems to suffer the same problem as 
>gnome-theme-manager. It won't come up until I kill or restart FAM.
>
>Tim
>
>
>
>_________________________________________________________________
>Add photos to your messages with MSN 8. Get 2 months FREE*.  
>http://join.msn.com/?page=features/featuredemail
>
>
is this the same fam that fills my logs with this crap:

Jan 23 21:09:03 visitoth xinetd[12707]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12707]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12708]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12708]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12709]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12709]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12710]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12710]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12711]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12711]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12712]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12712]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12713]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12713]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12714]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12714]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12715]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12715]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12716]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12716]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12717]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12717]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12718]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12718]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12719]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12719]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12720]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12720]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12721]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12721]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12722]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12722]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12723]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12723]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12724]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12724]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12725]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12725]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12726]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12726]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12727]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12727]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12728]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12728]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12729]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12729]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12730]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12730]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[12731]: warning: can't get client address: Transport 
endpoint is not connected
Jan 23 21:09:03 visitoth xinetd[12731]: libwrap refused connection to sgi_fam from <no 
address>
Jan 23 21:09:03 visitoth xinetd[1857]: Deactivating service sgi_fam due to excessive 
incoming connections.  Restarting in 30 seconds.
Jan 23 21:09:34 visitoth xinetd[1857]: Activating service sgi_fam

What the heck is all this nonsense?  It drives me bonkers...  It will do this, then 
keep quite for
several minutes to several hours, then fritz out again.  I look at my logs, and I 
can't see where
anything/anyone is trying to compromise my system.  It just fills my logs with this 
crap.



-Chuck S.


Reply via email to