Well, you just fixed only one of the problems by upgrading to xinetd-2.3.4. Actually, Trond Eivind Glomsrød (the xinetd package maintainer for redhat) is aware of these problems and is current trying to fix a bigger problem - that's is if he can convince the author of xinetd to allow it.
Here's the problem: 1. sgi_fam is an xinetd rpc service. When nautilus or konqueror lauch they make a connection to fam. All is fine. 2. When someone (or some program) decides to "/etc/rc.d/init.d/xinetd reload", the xinetd find it neccessary to give sgi_fam a new port number - this, of course, make nautilus or konqueror quit sync'ing with the filesystem because they just lost the connection to fam! They're left in limbo. Even if you say "chkconfig telnet off", which has nothing to do with an rpc service, xinetd will restart rpc services. Bottom line is that I believe xinetd is not handling the -HUP signal correctly in order to pick and choose which specific service needs to restart. -eric wood ----- Original Message ----- From: "Zhi-Wei Lu" <[EMAIL PROTECTED]> > It turns out to be a problem with xinetd. I was using redhat packaged > xinetd-2.3.3-1. After I compiled xinet-2.3.4 from (http://www.synack.net/xinetd/) > ,installed the xinetd binary, and restart xinetd. sgi_fam will stay alive if I do > > telnet localhost fam_port > > Thank you very much for your help. > > How can I file a bug report to redhat about xinetd-2.3.3-1? _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
