Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#25279 - [shorewall] /var/lock/subsys/shorewall': No such file or directory

Attached to Project: Arch Linux
Opened by Das (DasFox) - Wednesday, 27 July 2011, 06:58 GMT
Last edited by Evangelos Foutras (foutrelis) - Saturday, 30 July 2011, 09:28 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:/var/lock/subsys/shorewall': No such file or directory

Everything is up to date on my box as of today for Arch x86...


Additional info:
* package version(s)
shorewall-4.4.21.1-1


Steps to reproduce:

When Shorewall is started manually or at system startup, I see this information in the console or log;

/var/lock/subsys/shorewall': No such file or directory

THANKS
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Saturday, 30 July 2011, 09:28 GMT
Reason for closing:  Not a bug
Comment by Das (DasFox) - Wednesday, 27 July 2011, 06:59 GMT
Forgot to show you there is nothing in /var/lock on my box;

[root@arch ~]# cd /var/lock/
[root@arch lock]# ls



THANKS
Comment by Jelle van der Waa (jelly) - Wednesday, 27 July 2011, 08:51 GMT
Looks like your suffering from another bug, which i added in the bugreport
Comment by Evangelos Foutras (foutrelis) - Wednesday, 27 July 2011, 09:08 GMT
If you copied the sample shorewall.conf file from /usr/share/shorewall to /etc, you'll need to change the following:

LOGFILE=/var/log/messages.log
SUBSYSLOCK=/var/lock/shorewall
MODULE_SUFFIX=ko.gz

However, I strongly suggest you adjust the default files we install under /etc, instead of replacing them with any sample files.
Comment by Das (DasFox) - Wednesday, 27 July 2011, 21:56 GMT
Ahhh, well I run Shorewall in Slackware and just copied those files in and in shorewall.conf from the Developer the default is;

SUBSYSLOCK=/var/lock/subsys/shorewall

So I did not think that Arch would change the default value...

Why is Arch changing the default value and not leaving what the developer intended?


THANKS
Comment by Das (DasFox) - Thursday, 28 July 2011, 07:54 GMT
Hi,

So you think there's a bug since I have it saying already?

SUBSYSLOCK=/var/lock/subsys/shorewall


THANKS
Comment by Evangelos Foutras (foutrelis) - Thursday, 28 July 2011, 10:52 GMT
I don't consider this to be a bug. From shorewall.conf(5):

SUBSYSLOCK=[pathname]
This parameter should be set to the name of a file that the
firewall should create if it starts successfully and remove when it
stops. Creating and removing this file allows Shorewall to work
with your distribution's initscripts. For RedHat and OpenSuSE, this
should be set to /var/lock/subsys/shorewall. For Debian, the value
is /var/lock/shorewall and in LEAF it is /var/run/shorwall.

/var/lock/subsys is used in Red Hat; Arch uses /var/lock.

In general, you can't copy configuration files from another distribution and expect it to work; the defaults could be different and/or the software versions might not be the same.

Loading...