On 11/25/2012 09:37 AM, Tom Eastep wrote: > On 11/25/2012 09:02 AM, Tom Eastep wrote: >> On 11/25/2012 05:00 AM, Mr Dash Four wrote: >> >> Given that specifying a log level affects all rules in the macro (except >> NFLOG and ULOG), I wouldn't recommend specifying a log level. >> > > It would be trivial to restrict the affect of a log level to just bare > 'LOG' rules when a macro is used as a default action. If no one objects, > I'll go ahead and make that change.
In testing this change, I'm finding that specifying 'macro.Name' isn't working correctly. So for now, macros specified as a default action must not have names that conflict with the name of an action. -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 \________________________________________________ ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
