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 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'. Note that to execute the sequence of ipset commands that you want to execute, Shorewall must be in the stopped state. So the above sequence is appropriate if you want to reload your ipsets. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
