| Summary: | ASTERISK-27367: logger: We should call rotate_file on huge logs even if rotatestrategy is none. | ||
| Reporter: | Corey Farrell (coreyfarrell) | Labels: | |
| Date Opened: | 2017-10-22 13:55:07 | Date Closed: | 2017-10-23 12:16:02 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Core/Logging |
| Versions: | 13.17.2 GIT 15.0.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | 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. | ||
| Comments: | By: Corey Farrell (coreyfarrell) 2017-10-23 12:16:02.414-0500 On further review I think this is not a bug. | ||