Re: [Shorewall-users] locking processes left behind

[Tom E. <te...@sh...>]

On 04/11/2018 08:15 PM, Brian J. Murrell wrote:
> On Wed, 2018-04-11 at 19:09 -0700, Tom Eastep wrote:
>>
>> Did you read the 5.1.12.3 release notes?
> 
> Ahhh.  No.  I read the 5.1.12 release notes but didn't go any further
> when I didn't see it.  Should have really.
> 
>> 1)  Previously, the Shorewall[6][-lite] lock file was not always
>>     released when an error occurred. This resulted in:
>>
>>     - A warning message saying that a stale lock file has been
>> removed
>>     - 'lock' processes remaining after shorewall[6][-lite] terminated
>>       (only reported on OpenWRT).
>>
>>     That has been corrected so that the lock file is released at exit
>>     if it hasn't been released already.
> 
> Awesome.  Building it right now.  Which brings up the question... in a
> shorewall[6]-lite deployment the fix for this is 100% on the -lite
> side, yes?

No -- it requires the firewall script to be compiled with the fix, as
well as having the fix installed on the shorewall[6]-lite firewall.

> 
> As an aside, is shorewall maintained in any public git (or other SCM)
> repo?
> 

I see that Matt answered that in an earlier post.

-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
                      \_______________________________________________