On 04/11/2018 06:30 PM, Brian J. Murrell wrote: > On Wed, 2018-02-28 at 08:51 -0800, Tom Eastep wrote: >> >> There are quite a few, but they are only an issue for people who have >> to >> rely on the obscure 'lock' utility. The rest just get a 'stale lock >> file >> removed' message the next time that they run shorewall[6][-lite]. >> I'll >> try to come up with a fix against 5.1.12... > > Did any solutions for this end up making it into 5.1.12? >
Did you read the 5.1.12.3 release notes?
<quote?>
Problems corrected:
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.
</quote>
-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
------------------------------------------------------------------------------ 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 Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
