Brian J. Murrell wrote: > > But this is clearly a Ubuntu problem, not shorewall. The only thing > that could be remotely related to shorewall would be an RFE that pulled > that lockfile location up into a variable that a distro could easily > override and that a shorewall-lite installation could override for it's > own location as well (i.e. don't assume it's the same on every > shorewall-lite and shorewall installation). > > Because really, even if Ubuntu handn't decided to move that lock file > somewhere else, shorewall-lite for OpenWRT would still have to > create /var/lock (same flavour as the last hack we discussed). But > indeed, it would know what dir it had to create and would not be > dependent on the shorewall administrative system not having changed > that. > > I will bug Ubuntu about that little change. >
I've implemented a LOCKFILE option in shorewall.conf. It is currently only in 3.9 but I'll back-port it at least to 3.4. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
