I thought of another benefit to a shiny new XML format All the files could be merged into a single shorewall.xml file with different sections. <config> <adminisabsentminded>true</adminisabsentminded> </config> <rules> <rule> ... </rule> </rules> <tcclasses> ... </tcclasses> etc...
Again, this could optionally be accomplished with any format that can implement nested key-value pairs like json. I'm not familiar with yaml. On 9/25/2011 14:38, Steve Thompson wrote: > On Sun, 25 Sep 2011, Homer Parker wrote: > >> On Sun, 2011-09-25 at 08:49 -0700, Tom Eastep wrote: >>> I agree that the rules file, in particular, is outgrowing the columnar >>> format but I am reluctant to accept that XML is the answer. I worry >>> that if the ruleset is represented in XML, you won't be able to see the >>> forest for all of the trees. >> Please, no XML.. > +1000 > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2dcopy2 > _______________________________________________ > Shorewall-users mailing list > Shorewall-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/shorewall-users ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
