[asterisk-users] High verbose set at console effects the logger file "Full" - Why is that?

[Jim Dickenson]

-- 
Jim Dickenson
mailto:dickenson at cfmc.com

CfMC
http://www.cfmc.com/



On Dec 30, 2011, at 4:55 PM, Bruce B wrote:

> 
> One can set the verbose level as well as the debug level. These control how much log information is generated at all not where it is being written.
> 
> What do you mean by above? Can I see something in the logger.conf that will keep it always at certain verbose level regardless of what command I issue at CLI?

No the verbose command controls how much verbose stuff is output. The debug command controls how much debug stuff is output. These are absolute controls of that information. As I said in my original email you can turn off stuff going to the CLI with the logger mute command. That way you do not adjust the verbose level at all.

> 
> You see the problem I have is that Fail2ban reads the asterisk "full" log file. So, if I am playing on the CLI and then do "core set verbose 0" and exit the box and forget to set it back to 9 then Fail2ban stops working because the log file hasn't logged the attack.
> 
> I still think there is a way around this and I am missing a config. Why would anyone tie security logs to a mere CLI command?
> 
> Thanks again
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20111230/997ee958/attachment.htm>