You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2007/06/24 00:51:52 UTC

DO NOT REPLY [Bug 32534] - [crit] (98)Address already in use: make_sock: could not bind to port 80

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32534>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32534


mvolaski@aecom.yu.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




------- Additional Comments From mvolaski@aecom.yu.edu  2007-06-23 15:51 -------
This is not a bug, but it's actually TWO bugs.

First, configuration changes shouldn't cause a program to fail. That's apache's
fault. It should know how its configuration is changing, know how to handle a
configuration from a previous version.

Second, the message isn't true. There is no problem binding to any ports. Apache
is just getting multiple Listen directives. It should see this and report that
and not claim it can't bind to a port that is open and available.When there
really is some program other than Apache bound to the port, then this message is
valid.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org