Hi,
I've also seen this recently and haven't solved the problem.
Using Apache 1.3.2 and Squid 2 RELEASE.
I got around it by putting Apache on 127.0.01 port 81. My guess
(just a guess at this stage) is that Apache is also binding to the
machine's address thus preventing squid from listening there.
It's not totally satisfactory so if anyone has solved the problem
please let us know.
Cheers,
Simeon
Joakim Hartikainen wrote:
>
> Hi,
>
> I'm trying to run squid 2.0 as an httpd-accelerator on the same
> machine as the webserver (trying with both Netscape & Apache). I have
> tried the fix 20.3 from the FAQ, where you on the webserver define,
> Port 80
> Bindaddress 127.0.0.1
>
> and on the Squid server define,
> httpd_accel_host 127.0.0.1
> httpd_accel_port 80
>
> But I can't start up the Squid server after I have started the
> webserver and vice versa, becuase the port is already bind.
>
> Any hints ?.
>
> Regards,
> Joakim
>
> --
> Föreningssparbanken IT P&T
> Joakim Hartikainen
> Phone: +46 8 58595329
> E-mail: Joakim.Hartikainen@foreningssparbanken.se
>
>
-- --------------------------------------------------------------------- Simeon Walker, email: simeon@sbs.bangor.ac.uk School of Biological Sciences, phone: +44 (0)1248 383702 University of Wales, Bangor, fax: +44 (0)1248 371644 Gwynedd, LL57 2UW, UK. www: http://sbsweb.bangor.ac.uk/ ---------------------------------------------------------------------Received on Tue Oct 06 1998 - 05:51:40 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:42:21 MST