Re: [squid-users] Rearranging squid.conf file

I'm not putting the include file path in double quotes under
2.7STABLE6 and things are working fine here (although I can see a file
path with, say, spaces not working). Is 3.x any different in this
regard?

You do need an absolute path, however; using a relative path will
result in the file being search for relative to your wd. Theoretically
this isn't an issue if you're always launching squid from the same wd
(if, say, your initscript cd's to /usr/local/squid before launching),
but really isn't worth the trouble.

A better idea would be to making relative includes be relative to the
location of the calling config file.</feature-request>

-C

On May 4, 2009, at 9:49 AM, Kinkie wrote:

> The filename needs to be enclosed in double quotes..
> As far as I know, it can be used for any type of acl, but I have never
> used it for time acls.
>
> On 5/4/09, Oleg <blake-r_at_mail.ru> wrote:
>> 1 and 2 - yes, 3 - no (I'm not seen that for a while)
>>
>> acl <name> <type> <path_to_file>
>>
>> Jagdish Rao пишет:
>>> Hi,
>>>
>>> The squid.conf is now increased to a very long listing. Can I have
>>> the
>>> following
>>>
>>> 1. Instead of the ACL
>>>
>>> acl <user1> src <user1IP>
>>>
>>> Can I use an external file which will have the listing ?
>>>
>>> 2. Instead of the ACL
>>>
>>> acl <user1> proxy_auth <user1>
>>>
>>> Can I use an external file which will have the listing ?
>>>
>>>
>>> 3. Instead of the ACL
>>>
>>> http_access allow <useer1> <Time1> <user1IP>
>>>
>>> Can I use an external file which will have the listing ?
>>>
>>> Thanks
>>>
>>> Regards
>>>
>>> Jagdish
>>>
>>>
>>>
>>> ##############################################################################################################################################
>>> The information transmitted is intended for the person or entity
>>> to which
>>> it is addressed and may contain confidential and/or privileged
>>> material. Any review, retransmission, dissemination, copying or
>>> other use
>>> of, or taking any action in reliance upon, this information by
>>> persons or entities other than the intended recipient is
>>> prohibited. If
>>> you have received this in error, please contact the sender and
>>> delete
>>> the material from your system. Accord Software & Systems Pvt. Ltd.
>>> (ACCORD) is not responsible for any changes made to the material
>>> other
>>> than those made by ACCORD or for the effect of the changes on the
>>> meaning
>>> of the material.
>>> ##############################################################################################################################################
>>>
>>> .
>>>
>>
>>
>
>
> --
> /kinkie
>
Received on Mon May 04 2009 - 16:09:56 MDT