Re: [Shorewall-users] locking processes left behind

2018-04-11 Thread Matt Darfeuille
On 4/12/2018 5:15 AM, 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

Re: [Shorewall-users] locking processes left behind

2018-04-11 Thread Brian J. Murrell
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

Re: [Shorewall-users] locking processes left behind

2018-04-11 Thread Tom Eastep
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

Re: [Shorewall-users] locking processes left behind

2018-04-11 Thread Brian J. Murrell
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