On 11/6/18 4:29 AM, ObNox wrote:
> Hi,
>
> Shorewall : 5.2.1.1
>
> I've decided to modularize Shorewall's configuration to keep things
> readable as they get more complicated.
>
> While testing, I use another configuration directory base and use
> "compile" to compare final results against the original ones.
>
> Shell# shorewall -v2 compile /path/to/oher-config newresult.firewall
>
> Withing "params" file, I include files from a subdirectory and to make
> sure I'm in the right directory, I use the internal "${g_confdir}"
> variable.
>
> Unfortunately, "${g_confdir}" is always set to "/etc/shorewall", no
> matter what the "[directory]" argument of "compile" is set to which
> makes the compilation fail (as the included files could not be found).
>
> Shouldn't all options accepting a "[directory]" argument set the
> internal "${g_confdir}" variable to the specified directory?
> No. Specifying a directory simply pushes that directory onto the front of the CONFIG_PATH. -Tom -- Tom Eastep \ Q: What do you get when you cross a mobster with Shoreline, \ an international standard? Washington, USA \ A: Someone who makes you an offer you can't http://shorewall.org \ understand \_______________________________________________
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
