>> In other words, VARDIR in shorewallrc is different from VARDIR everywhere
>> else? And you don't find that the least bit confusing?
>>
>
> It is confusing when discussing internals. I'll change the code someday
> to use a different variable name.
>
You can introduce VARLIB (new variable) in shorewallrc to point to
"/var/lib" and in the same shorewallrc file to change the existing
VARDIR to point to ${VARLIB}/$PRODUCT. That way, there is no confusion
as to the meaning of these two variables and when I source shorewallrc I
know exactly what I am getting.
As it stands though, when I am debugging the code produced by any
shorewall product and come across VARDIR, I don't know what the hell is
that: is it ${VARDIR}/$product or is just the original $VARDIR from
shorewallrc.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
