[asterisk-dev] [Code Review] Logger does not warn of failure to open logging channels

[mjordan]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/1338/#review4041
-----------------------------------------------------------



trunk/main/logger.c
<https://reviewboard.asterisk.org/r/1338/#comment7956>

    Not your change, but blob.



trunk/main/logger.c
<https://reviewboard.asterisk.org/r/1338/#comment7955>

    BLOB!


- mjordan


On Aug. 11, 2011, 10:45 a.m., opticron wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/1338/
> -----------------------------------------------------------
> 
> (Updated Aug. 11, 2011, 10:45 a.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Summary
> -------
> 
> Currently, logger only prints an error message to stderr when it fails to open a logger channel where many users will not see it because the logger lock is held.  The alternative provided by this patch is to log the error to all attached consoles in the hopes that it will be easier to see.  Additionally, this patch prevents the failed logger channel from being added to the list where it would silently fail on each call to the Asterisk logger.
> 
> 
> This addresses bug ASTERISK-16231.
>     https://issues.asterisk.org/jira/browse/ASTERISK-16231
> 
> 
> Diffs
> -----
> 
>   trunk/main/logger.c 331573 
> 
> Diff: https://reviewboard.asterisk.org/r/1338/diff
> 
> 
> Testing
> -------
> 
> Verified that the stderr log was the only thing printed for failed logger channels.  Verified that the patch provides warning to indirect consoles (not using the -c option).
> 
> 
> Thanks,
> 
> opticron
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20110811/3a207976/attachment.htm>