Re: Solved(I think) Re: FC7->FC8 upgrade yields apache error: (98)Address already in use: make_sock: could not bind to address [::]:80
- From: "Eric H." <REMOVE-CAPSburnFORout@xxxxxxxxxxxxxx>
- Date: Wed, 14 Nov 2007 14:16:37 -0500
Ivan Marsh wrote:
Moving data from where it's expected can hardly be called a bug.
Doc it hurts when I do this.
If the path was hard coded in the apache binary then I might agree with
you but it's not; it's in httpd.conf for a reason so my assertion
stands, it's a bug with the "service" command.
.
- Follow-Ups:
- References:
- FC7->FC8 upgrade yields apache error: (98)Address already in use: make_sock: could not bind to address [::]:80
- From: Eric H.
- Re: FC7->FC8 upgrade yields apache error: (98)Address already in use: make_sock: could not bind to address [::]:80
- From: Eric H.
- Solved(I think) Re: FC7->FC8 upgrade yields apache error: (98)Address already in use: make_sock: could not bind to address [::]:80
- From: Eric H.
- Re: Solved(I think) Re: FC7->FC8 upgrade yields apache error: (98)Address already in use: make_sock: could not bind to address [::]:80
- From: Ivan Marsh
- FC7->FC8 upgrade yields apache error: (98)Address already in use: make_sock: could not bind to address [::]:80
- Prev by Date: Re: Solved(I think) Re: FC7->FC8 upgrade yields apache error: (98)Address already in use: make_sock: could not bind to address [::]:80
- Next by Date: Re: Solved(I think) Re: FC7->FC8 upgrade yields apache error: (98)Address already in use: make_sock: could not bind to address [::]:80
- Previous by thread: Re: Solved(I think) Re: FC7->FC8 upgrade yields apache error: (98)Address already in use: make_sock: could not bind to address [::]:80
- Next by thread: Re: Solved(I think) Re: FC7->FC8 upgrade yields apache error: (98)Address already in use: make_sock: could not bind to address [::]:80
- Index(es):
Relevant Pages
|
