[asterisk-bugs] [JIRA] (ASTERISK-24817) init_logger_chain: unreachable code block

[Corey Farrell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Corey Farrell updated ASTERISK-24817:
-------------------------------------

    Attachment: logger-unreachable.patch

Just does not seem like Asterisk should run without real logging (to a file) unless the admin explicitly sets it up that way (with a valid logger.conf).  I don't feel that strongly about this.  I posted here to allow someone to disagree with me, and Matt has.  That's good enough.

The patch I have is attached.  I don't have a chance to test this now (beyond knowing it compiles).  Hopefully I'll get around to testing next week.

> init_logger_chain: unreachable code block
> -----------------------------------------
>
>                 Key: ASTERISK-24817
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24817
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Logging
>    Affects Versions: SVN, 11.16.0, 13.2.0
>            Reporter: Corey Farrell
>            Severity: Minor
>         Attachments: logger-unreachable.patch
>
>
> init_logger_chain returns immediately if logger.conf was not found or for parse errors.  Later the procedure has an unreachable block that would set default console logging if no config was found.
> In 11 and 13 I think the console logger should be applied if logger.conf is missing or invalid during startup only.  During failed reload we should just return as it does now.
> In trunk I think this should be a fatal error during startup, and the unreachable code should be removed.  Failed reload's should continue to be a no-op.



--
This message was sent by Atlassian JIRA
(v6.2#6252)