Summary: | net-firewall/shorewall-4.4.23.2 - /etc/init.d/shorewall: touch: cannot touch "/var/lock/subsys/shorewall": No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Aleš Krajník <software> |
Component: | Current packages | Assignee: | Vieri <rentorbuy> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | burcheri.massimo+bugs-gentoo, netmon |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Aleš Krajník
2012-08-04 02:16:13 UTC
As far as I see this, this is not a shorewall specific issue. Other programs may use subsys or other subdirectories of /var/lock, too. I would propose, that you create this directory upon boot, by adding the appropriate line to some early running initscripts, like bootmisc. Wouldn't it be possible for the init script to check for the directory existence, let's say, using "checkpath" in the init script or in /sbin/shorewall? I thought every script should check its "substantial" directories. Maybe this one is not substantial, or maybe the problem could be in tmpfs overwriting the /run directory... I am having similar issue with BIND - so using tmpfs could be it. However, as I said, this is a fresh installation and not my first. The previous installations of mine were before /run being on tmpfs. (older openrc) I just thought shorewall init script could make all necessary checks as all needed tools (checkpath) are present and easy to use. In my opinion the problem is in your setup with tmpfs, so for me it's a wontfix. You can file a bug with shorewall, if you think, that it should check for this directory. (In reply to comment #3) > In my opinion the problem is in your setup with tmpfs, so for me it's a > wontfix. > You can file a bug with shorewall, if you think, that it should check for > this directory. As of baselayout 2.1-r1 /run is mounted as tmpfs on every boot, hence why the stuff located there gets clobbered. Heck, the ebuilds for 2.1-r1 and the current 2.2 both give a warning that it'll be remounted as such when you reboot, Yes this requires a checkpath -d on the init script, since we're now defaulting to tmpfs-based /run (for other reasons). Sorry, my mistake. Fixed in 4.5.8.2-r1. It's an unstable version, but I'll try to get it stable as soon as possible. Shouldn't we set the default in shorewall.conf to something appropriate for Gentoo like this: SUBSYSLOCK=/var/run/lock/subsys/shorewall This bug has reared its head again in net-firewall/shorewall-4.5.18 |