On Wed, 14 Mar 2001, Nathalie Boulos spewed into the bitstream:
NB>Chuck, you might be right. Because, identd is launched at init, and I have
NB>the following line in the /etc/inet.conf :
NB>
NB>auth stream tcp wait root /usr/sbin/in.indentd in.indentd -e -o
NB>
NB>Do you suggest I remove that line, then restart inetd?
Just put a # sign in front of that line.
NB>The error in the messages log might disappear, but you think that the server
NB>will respond more quickly (because my initial problem is that my linux
NB>servers take some time to reply)?
How many hosts are on your LAN?
NB>----- Original Message -----
NB>From: Chuck Mead <[EMAIL PROTECTED]>
NB>To: <[EMAIL PROTECTED]>
NB>Sent: Wednesday, March 14, 2001 2:53 PM
NB>Subject: Re: My Linux server takes time to reply
NB>
NB>
NB>> On Wed, 14 Mar 2001, Mike Burger spewed into the bitstream:
NB>>
NB>> MB>The server is taking so long to reply because it can not resolve your
NB>IP
NB>> MB>address against a domain name.
NB>> MB>
NB>> MB>The reason is that your DNS server appears to not be running. That
NB>> MB>message appears to show that you're trying to run BIND from within
NB>> MB>inetd...and if so, that's the incorrect way to do it. BIND (named)
NB>should
NB>> MB>be run as a standalone service.
NB>>
NB>> Mike... I don't think it's talking about BIND... I think it's saying
NB>> that the service in question cannot "bind" to the interface because it
NB>> already is (e.g. it's already running). The problem is that too much of
NB>> the message has been cut away to define which services it is that's
NB>> causing the trouble.
NB>>
NB>> I suspect that this is an issue with the ident daemon. This is caused
NB>> because it get's started in init (not inetd) as a stand-alone service
NB>> and then it gets enabled in inetd as well. Needless to say you cannot
NB>> run the same service twice... without getting the "Address already in
NB>> use" error message!
NB>>
NB>> MB>On Wed, 14 Mar 2001, Nathalie Boulos wrote:
NB>> MB>
NB>> MB>> Hi,
NB>> MB>>
NB>> MB>> I have a Red Hat 6.2 running as a sendmail and apache web server
NB>> MB>on a LAN.
NB>> MB>> When I try to connect to my server by telnet,ftp , to retrieve
NB>> MB>my mail or to connect to the web server, linux takes time to
NB>> MB>reply. Though I'm working on the same LAN.
NB>> MB>>
NB>> MB>> I have the following error message in the /var/log/messages file:
NB>> MB>>
NB>> MB>> "... inetd[pid] : auth/tcp : bind : Address already in use"
NB>> MB>>
NB>> MB>> I would greatly appreciate if someone helps me to find out the
NB>> MB>cause of this error and why the server is late to reply.
--
Chuck Mead, csm -AT- moongroup.com, Owner, MoonGroup.com
(Note: html formatted email sent to me is filtered & deleted unread)
GnuPG Public Key Available: http://wwwkeys.us.pgp.net
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
