On 05/04/2013 08:35 AM, Dash Four wrote:
>
> Tom Eastep wrote:
>> If you 'sh -x ${SBINDIR}/shorewall restart' and look for the call to the
>> function 'uptodate', you can see which file on your CONFIG_PATH is
>> triggering the recompile.
>>
> You may be on to something... Here is what I've discovered: My init.d
> shorewall script has the following command line during start:
>
> $shorewall $OPTIONS start $config_file_dir 2>&1 | $logger
>
> $shorewall is, as you rightly guessed, "/usr/sbin/shorewall". $OPTIONS
> used to be "-V0", but I changed it to "-V1" to see what is happening.
> $config_file_dir is set as "/etc/shorewall". Now, when I have this
> command line shorewall *always* recompiles without fail. However, when I
> execute "$shorewall $OPTIONS start" (without the config_file_dir
> parameter), then everything seems to be OK.
>
> When I follow your advice above and do "sh -x $shorewall $OPTIONS start
> 2>&1 | $logger" there is no problem with it either. So, could it be that
> when "config_file_dir" is specified shorewall does something which isn't
> supposed to be doing?
> Shorewall ignores the setting of AUTOMAKE when a directory name is specified on the run-line. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
