On Wed, 2018-04-11 at 19:09 -0700, Tom Eastep wrote:
> Did you read the 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?

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


Attachment: signature.asc
Description: This is a digitally signed message part

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Shorewall-users mailing list

Reply via email to