squid bind to port 80 fails when started via squid.sh script

P.U.Kruppa root at pukruppa.de
Wed Jul 6 15:35:48 GMT 2005


On Wed, 6 Jul 2005, Wayne Sierke wrote:

> On Wed, 2005-07-06 at 03:33 +0200, P.U.Kruppa wrote:
>> On Wed, 6 Jul 2005, Wayne Sierke wrote:
>>
>>> FreeBSD 5.4-RELEASE/squid-2.5.9_3
>>>
>>> If I start squid via the script (as root), I get:
>>>
>>> /var/log/squid_cache.log:
>>>
>>> commBind: Cannot bind socket FD 11 to *:80: (13) Permission denied
>>> FATAL: Cannot open HTTP Port
>>> Squid Cache (Version 2.5.STABLE9): Terminated abnormally.
>> Did you set
>> squid_enable="YES"
>
> Yes.
>
>> squid_user="root"
>
> No, it didn't occur to me. I was assuming that the script would set it
> to the required user and I didn't see any documentation about it.
> However I can now see that it should probably be self-evident for even a
> semi-competent user. :)
I have no idea. Being a semi-competent user myself - I worked 
this out by trial and error because I had to set up a transparent 
proxy these days.


Regards,

Uli.

>> squid_flags="-D"
>
> No. It's the default in the script.
>
>> in /etc/rc.conf ?
>>
>> Regards,
>>
>> Uli.
>
> Just so I can learn a bit more from this - has this script been designed
> like this because it is specifically safer to launch the squid
> executable as user 'squid'? Or is it just because it's the 'norm' to
> avoid running programs (from launch scripts) as root whenever possible?
>
>
> Thanks for your help,
>
> Wayne
>
>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>



*********************************************
* Peter Ulrich Kruppa - Wuppertal - Germany *
*********************************************


More information about the freebsd-questions mailing list