-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix logrotate empty file hole issue #1561
fix logrotate empty file hole issue #1561
Conversation
trunk/etc/logrotate.d/srs Can you only submit the modifications to the log code? It would be better to place this file in the wiki or issue, as everyone's logrotate configuration may be different.
|
/data/log/srs/*.log { weekly size 200M copytruncate rotate 5 dateext noolddir }
logrotate file removed from the repo. /etc/logrotate.d./srs
|
I need to update the document. I will take some time to update the document first before merging this PR. Thanks again 👍
|
I think this logrotate issue causing file fragmentation should be resolved. It's great! After thinking about this, the previous logic was to create a file if it doesn't exist when opening it. I wonder if it would be better to merge it into a single "open" operation? Perhaps this would be a more appropriate way to make the change.
Could you consider this improvement?
|
I took a look, and these two sentences can be combined as:
Below is an example program for reference:
First write:
Continuing to write if the file exists for the second time:
|
Wiki:
I will first merge this PR and then make one more code modification. Thanks @wnpllrzodiac
|
Improvement PR: 731e878
|
I remember discussing this issue with the author in the issue thread. I have submitted a pull request, you can search for it. You mentioned 'one of them,' but I'm not quite clear, are there no issues with the others?
Get BlueMail for Android
On July 2, 2020, at 09:55, Qiao Lin ***@***.***> wrote:
I deployed version 3.0 of the k8s cluster, and on one of the host machines, I used the copytruncate method to rotate the logs. However, I encountered the phenomenon of sparse files. Is it possible that version 3.0 release 0 does not support the copytruncate method yet, and currently only supports version 2.0?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#1561 (comment)
`TRANS_BY_GPT3`
|
refer to #1554