On Wed, 14 Mar 2001, Mike Burger spewed into the bitstream:
MB>The server is taking so long to reply because it can not resolve your IP
MB>address against a domain name.
MB>
MB>The reason is that your DNS server appears to not be running. That
MB>message appears to show that you're trying to run BIND from within
MB>inetd...and if so, that's the incorrect way to do it. BIND (named) should
MB>be run as a standalone service.
Mike... I don't think it's talking about BIND... I think it's saying
that the service in question cannot "bind" to the interface because it
already is (e.g. it's already running). The problem is that too much of
the message has been cut away to define which services it is that's
causing the trouble.
I suspect that this is an issue with the ident daemon. This is caused
because it get's started in init (not inetd) as a stand-alone service
and then it gets enabled in inetd as well. Needless to say you cannot
run the same service twice... without getting the "Address already in
use" error message!
MB>On Wed, 14 Mar 2001, Nathalie Boulos wrote:
MB>
MB>> Hi,
MB>>
MB>> I have a Red Hat 6.2 running as a sendmail and apache web server
MB>on a LAN.
MB>> When I try to connect to my server by telnet,ftp , to retrieve
MB>my mail or to connect to the web server, linux takes time to
MB>reply. Though I'm working on the same LAN.
MB>>
MB>> I have the following error message in the /var/log/messages file:
MB>>
MB>> "... inetd[pid] : auth/tcp : bind : Address already in use"
MB>>
MB>> I would greatly appreciate if someone helps me to find out the
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