[MXS-1322] Flushing log should reopen, not reopen and truncate. Created: 2017-07-24  Updated: 2017-08-08  Resolved: 2017-08-08

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.1.4
Fix Version/s: 2.2.0

Type: Bug Priority: Minor
Reporter: Johan Wikman Assignee: Johan Wikman
Resolution: Fixed Votes: 0
Labels: None


 Description   

When issuing

MaxScale> flush logs

the log file is closed and then reopened and truncated.

That means that unless the file has been moved first, data will be lost.

The command should just cause the file to be reopened and if you want to reset the file you should manually remove the file and then issue flush logs or just

$ truncate -s 0 maxscale.log


Generated at Thu Feb 08 04:05:52 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.