> It depends on which command is being executed.
>
> However, I just thought of a foolproof trick - If you really want to
> relocate shorewall.conf, place this in /etc/shorewall/shorewall.conf:
>
>       INCLUDE /path/to/my/shorewall.conf
>   
Haven't thought of that before, thanks for the tip!

> In your 'real' shorewall.conf, be sure to modify CONFIG_PATH so that it
> looks in your private config directory first.
>   
That's the first thing I did in my own version of shorewall.conf - I use 
a (secured) directory where I place all 'sensitive' files (that includes 
all shorewall configuration files) and the internal/application path 
(not the execute path!) is the first thing I changed and I am sure this 
is picked up by Shorewall.


------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to