| Summary: | =net-firewall/shorewall-3.2.9 stabilization | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Markus Ullmann (RETIRED) <jokey> |
| Component: | New packages | Assignee: | 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)
2007-04-12 18:32:19 UTC
sparc stable, been using it for some time now without issues. 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. both stable on amd64 Both net-firewall/shorewall{,-lite}-3.2.9 stable for HPPA.
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
ppc64 stable Stable on Alpha. Leaving it to maintainer to close bug due to comment #5. (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. |