Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 475428 - net-firewall/shorewall* - init.d script should read status from /sbin/shorewall*
Summary: net-firewall/shorewall* - init.d script should read status from /sbin/shorewall*
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Server (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Vieri
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-01 14:56 UTC by Thomas Deutschmann (RETIRED)
Modified: 2013-08-29 18:44 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Deutschmann (RETIRED) gentoo-dev 2013-07-01 14:56:23 UTC 
Hi,

shorewall provides an "SUBSYSLOCK" option, which isn't honored by the init script. From man page:

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, this should be set to /var/lock/subsys/shorewall. For Debian, the value is /var/state/shorewall and in LEAF it is /var/run/shorwall.

Reproducible: Always

Steps to Reproduce:
1. /etc/init.d/shorewall start
2. /sbin/shorewall stop
3. /etc/init.d/shorewall status
Actual Results:  
The init script reports, that shorewall is still running.

Expected Results:  
The init script should read the status from '/sbin/shorewall status'. In that case, we stopped shorewall, so the init script should'n report shorewall is still running.
Comment 1 Constanze Hausner (RETIRED) gentoo-dev 2013-08-29 18:44:34 UTC 
Fixed in 4.5.19 by Thomas himself. Thank you Thomas :).