>> C_MACRO >> ~~~~~~~ >> LOG >> AUDIT(drop) >> NFLOG(1,0,1):debug >> > > That isn't valid. 'debug' only applies to the LOG target, not the NFLOG > target. So the macro handler already excludes NFLOG from the targets > that inherit a level from the macro invocation. > Yeah, I agree - bad example, but you get the gist of it.
> True. But I'm not sure that is the desired behavior in the context of a > default action. Default actions were created primarily to suppress > unwanted log noise, not to amplify it. > Why do you have to make a distinction between "default" action/macros and user-defined ones in the context of logging levels? My thinking, as indicated in the previous post, is that if user wants to pass a log level down to all log statements in that macro - they should be able to, let them. ------------------------------------------------------------------------------ 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
