Hmm.. I find this strange since it's my understanding that httpd does
bind itself to port 80 by default, without it how else can it respond to
http requests?
The httpd error would also not be displayed if it was not attempting
bind to the port.
Michael.
-----Original Message-----
From: Sharad Joshi [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 6 April 1999 17:13
To: Michael Mansour
Cc: '[EMAIL PROTECTED]'
Subject: Re: tproxy, firewall and httpd
+ rules script the httpd port 80 service stops working (web pages can't
be
+ accessed) and when trying to restart httpd the following error occurs:
+
+ bind: Address already in use
+ httpd: could not bind to port 80
just a few days back, a mail similar to this was posted to the list. The
moral of the answers was httpd used some other port. Can anyone explain,
if httpd does not use this port, who does? My /etc/services has lines:
www 80/tcp http # WorldWideWeb HTTP
www 80/udp # HyperText Transfer Protocol
what does that mean, if it is not httpd.
S.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
