On 9/17/10 7:00 AM, Mr Dash Four wrote: > >> Which only confirms what I wrote -- any system that runs Shorewall must >> have /etc/shorewall/shorewall.conf; but you are correct that it can be a >> minimal file. >> > I am curious though - is there any reason to have this restriction? This > 'configuration' file with just ENABLE_STARTUP=Yes (while for all other > options my own shorewall.conf is picked up) does not really make sense > to me.
It's the way that Shorewall works and the cost of changing it is high enough that it's just not worth the effort. Your modification to /etc/init.d/shorewall only works on commands issued through that script. Unless your log file happens to be in the default place, even simple CLI commands like 'shorewall show log' won't work. The rules compiler is the only part of Shorewall that uses the directory specified in the 'start' and 'restart' commands. -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
