On 1/14/2018 6:47 PM, Brian J. Murrell wrote: > On Sun, 2018-01-14 at 17:06 +0100, Matt Darfeuille wrote: >> >> The code is only working and tested on OpenWRT. > > Which is my platform. > >> Lock on OpenWRT has limited functionalities. > > Such as what? And why would it being limited (only) on OpenWRT mean > you that make it's use exclusive to OpenWRT. > > Does any of the limited functionalities shed any light on how a lock > can be running without the file it's trying to lock being present?
Ok -- You seem to be fixated on not restricting the use of the lock utility. > To be clear, the file is still there, it's just that it's directory entry > has been removed. So something removed it without unlocking it? > As I don't see this conversation going anywhere I'll just say the following: 1) I don't get that behavier on OpenWRT 15.05.1 with shorewall-lite 5.1.10.2. Note that Shorewall is patched: 1a68d87c9 c518cfaa4 09980cc75 e0a757ea0 550003f0f 2) Using /etc for temporary files. -Matt -- Matt Darfeuille ------------------------------------------------------------------------------ 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
