Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 174312

Summary: =net-firewall/shorewall-3.2.9 stabilization
Product: Gentoo Linux Reporter: Markus Ullmann (RETIRED) <jokey>
Component: New packagesAssignee: Gentoo Netmon project <netmon>
Status: RESOLVED UPSTREAM    
Severity: normal CC: sebastian_ml
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Markus Ullmann (RETIRED) gentoo-dev 2007-04-12 18:32:19 UTC
Please test and mark stable
Comment 1 Gustavo Zacarias (RETIRED) gentoo-dev 2007-04-12 18:36:06 UTC
sparc stable, been using it for some time now without issues.
Comment 2 Markus Ullmann (RETIRED) gentoo-dev 2007-04-12 18:55:33 UTC
as the shorewall-lite ebuilds provide a subset of the same stuff, please also keyword stable there as well even if your arch is not added yet.
Comment 3 Peter Weller (RETIRED) gentoo-dev 2007-04-12 19:42:24 UTC
both stable on amd64
Comment 4 Jeroen Roovers (RETIRED) gentoo-dev 2007-04-13 08:13:18 UTC
Both net-firewall/shorewall{,-lite}-3.2.9 stable for HPPA.
Comment 5 Sebastian 2007-04-14 13:33:40 UTC
Hello all,

I upgraded to 3.2.9 and initially shorewall wouldn't start because /sbin/shorewall sets up its init file in a /var directory that's mounted noexec. Here's the part of the start_command function that's responsible:

if $SHOREWALL_SHELL ${SHAREDIR}/compiler $debugging $nolock compile ${VARDIR}/.start; then
            ${VARDIR}/.start $debugging start

I changed the line to
            /bin/sh ${VARDIR}/.start $debugging start
and now it works. Previous stable shorewall versions didn't show this behaviour. Should this issue be addressed through a bug report or is it something the user has to deal with on his own?

Regards
Sebastian
Comment 6 Markus Rothe (RETIRED) gentoo-dev 2007-04-15 19:18:48 UTC
ppc64 stable
Comment 7 Bryan Østergaard (RETIRED) gentoo-dev 2007-04-16 23:53:15 UTC
Stable on Alpha. Leaving it to maintainer to close bug due to comment #5.
Comment 8 Markus Ullmann (RETIRED) gentoo-dev 2007-04-22 15:47:30 UTC
(In reply to comment #5)
> I upgraded to 3.2.9 and initially shorewall wouldn't start because
> /sbin/shorewall sets up its init file in a /var directory that's mounted
> noexec. Here's the part of the start_command function that's responsible:

Okay, two parts are involved here:
a) you mounted it no-exec, that breaks some apps
b) as this is set by shorewall itself, upstream changed their mind about it

so resolution is:
- partly up to you as you mounted /var with noexec flag
- ask / notify upstream (shorewall developers) about this

You can add this bug report as reference if you want, marking it as UPSTREAM as its not gentoo-specific.
Feel free to reopen this bug in case upstream changes something about it.