>>>>> Another note -- when someone sends me a problem configuration, the
>>>>> *first*
>>>>> thing I do is edit the shorewall.conf file and set
>>>>> CONFIG_PATH=/usr/share/shorewall/ (that's where I install Shorewall
>>>>> --YMMV).
>>>> As I already pointed out, my "CONFIG_PATH=.:/usr/share/shorewall"
>>>> (that's
>>>> the config path in shorewall.conf which resides in my test case
>>>> directory), so I don't see why shorewall decided not to honour this
>>>> setting and started looking in /etc/shorewall for whatever reason.
>>>>
>>>> Besides, setting "CONFIG_PATH=/usr/share/shorewall" in shorewall.conf
>>>> still gets me "/usr/share/shorewall/lib.cli-std: line 41:
>>>> /etc/shorewall/params: Permission denied".
>>> That looks like /etc/shorewall is still in the CONFIG_PATH.
>> Whatever it is, it is not from my shorewall.conf as evident from what I
>> posted above. The question is - if it isn't my own shorewall.conf, what
>> is it? Whatever it is, or whatever shorewall is doing in not honouring
>> either that config path or the path specified on the command line
>> ("shorewall compile -e . firewall"), it is wrong.
>>
>>> I wouldn't be able to support Shorewall at all if this problem was
>>> ubiquitous. So something in your config is directing the compiler to
>>> /etc/shorewall.
>> If you can't tell what it is (and you wrote that software), then what
>> hope is left for any of us? If it isn't shorewall.conf, and it isn't the
>> path specified on the command line either, then what is it?
>
> The answer is on your computer, not mine.
Which is what exactly (provided you know it, that is)?
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
