My shorewall init script has a conditional block on $COMMAND = start and
it wipes out all my existing ipsets (flushes them first) with 'ipset -F'
and 'ipset -X' and then reloads them from a predefined script.
That's all well and good, but when I do 'service shorewall reload' it
does not pass
On 9/29/10 4:07 PM, Mr Dash Four wrote:
My shorewall init script has a conditional block on $COMMAND = start and
it wipes out all my existing ipsets (flushes them first) with 'ipset -F'
and 'ipset -X' and then reloads them from a predefined script.
That's all well and good, but when I do
What do you mean by 'init script'? Do you mean /etc/init.d/shorewall or
do you mean /etc/shorewall/init?
/etc/shorewall/init (it relies on $COMMAND = start to do its job)
--
Start uncovering the many advantages of
On 9/29/10 4:29 PM, Mr Dash Four wrote:
What do you mean by 'init script'? Do you mean /etc/init.d/shorewall or
do you mean /etc/shorewall/init?
/etc/shorewall/init (it relies on $COMMAND = start to do its job)
Then is sounds like /etc/init.d/shorewall is generating '/sbin/shorewall
Then is sounds like /etc/init.d/shorewall is generating '/sbin/shorewall
stop; /sbin/shorewall start' for the 'reload' command. So
/etc/shorewall/init will be invoked twice; once with $COMMAND=stop and
once with $COMMAND=start. That's the way it works and there is nothing
to 'fix'.
On 9/29/10 4:52 PM, Mr Dash Four wrote:
Then is sounds like /etc/init.d/shorewall is generating '/sbin/shorewall
stop; /sbin/shorewall start' for the 'reload' command. So
/etc/shorewall/init will be invoked twice; once with $COMMAND=stop and
once with $COMMAND=start. That's the way it works
On 9/29/10 5:09 PM, Tom Eastep wrote:
I have no idea what's going on on your system.
gateway:~# cat /etc/shorewall/init
#
# Shorewall version 4 - Init File
#
# /etc/shorewall/init
#
# Add commands below that you want to be executed at the beginning of
# a shorewall start or
I have no idea what's going on on your system.
This is all very strange. After being able to reload shorewall a couple
of times (with NO errors, i.e. shorewall executing as it should), I
changed my rules file a couple of times, then loaded a few ipsets I
needed to test (see below) and
On 9/29/10 5:52 PM, Mr Dash Four wrote:
I have no idea what's going on on your system.
This is all very strange. After being able to reload shorewall a couple
of times (with NO errors, i.e. shorewall executing as it should), I
changed my rules file a couple of times, then loaded a few
