Feature request: Log file size limit and total size cap rotation options

[tastyratz]

Is there already an issue for this request?

• [X] I have checked older issues, open and closed

Platform

All

Describe the enhancement you'd like

NZBget does have a time based rotation, however, it has no control over runaway logs. This has, on multiple occasions, meant that a failure or error creating logs that are many GB in size that completely overrun disk space. The solution to this would be some intelligence that

1. Limits logs to a manaegable file size such as 500mb or 1gb
2. Limits the total log space to a user defined limit. If I was able to configure NZBGet to rotate logs once the total logging space consumes 2GB for example I would not wake up with a server full of crashed services and a full C drive because some servers were spitting out errors over the course of a day or 2.

While NZBget has a log retention policy it does not have a maximum log limit policy. I propose this also exist

Extra information

No response

[tastyratz]

Just to provide additional context, this just took me down, again, shortly after opening this request

I'm now trying to rebuild and repair this machine again since Windows does not take kindly to having zero space available.

I just inspected these logs. I would say about 80% of the entries are sequential and almost identical with only the timestamp and onf of the column numbers sometimes being different

Fri Mar 29 06:35:20 2024 4572 35464 DEBUG decrypted: cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc (RarReader.cpp:691:RarVolume::DecryptBuf)