[asterisk-bugs] [JIRA] (ASTERISK-27367) logger: We should call rotate_file on huge logs even if rotatestrategy is none.

[Corey Farrell (JIRA)]

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

Corey Farrell updated ASTERISK-27367:
-------------------------------------

    Comment: was deleted

(was: Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].)

> logger: We should call rotate_file on huge logs even if rotatestrategy is none.
> -------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27367
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27367
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Logging
>    Affects Versions: 13.17.2, GIT, 15.0.0
>            Reporter: Corey Farrell
>            Severity: Minor
>
> In {{reload_logger}} we call {{rotate_file}} on files that exceed 1gb, but only if {{rotatestrategy != NONE}}.  This is incorrect as we could be using {{exec_after_rotate}} to signal an external process to perform rotation.



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