It seems that specifying an alternate config directory works for everything except shorewall.conf
Given that some of the global settings in tehre might be things you would want to try changes to, it seems very inconvinient to not be able to try an alternate shorewall.conf file as part of a new config. At least I haven't found any commandline argument or environment variable or anything else that I can use to convince shorewall that I really really realy do NOT want it to look at /etc/shorewall/shorewall.conf Did I miss something? If this isn't supported, would you accept a patch to fix this inconsistency? -- Len Sorensen ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
