-
-
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
srs 2.0 logrotate copytruncate generates file holes #1554
Comments
wnpllrzodiac
pushed a commit
to wnpllrzodiac/srs
that referenced
this issue
Jan 6, 2020
This was referenced Jan 6, 2020
winlinvip
pushed a commit
that referenced
this issue
Jan 8, 2020
* fix logrotate empty file hole issue refer to #1554
winlinvip
added a commit
that referenced
this issue
Jan 8, 2020
winlinvip
added a commit
that referenced
this issue
Jan 9, 2020
I deployed version 3.0 of k8s cluster, and on one of the host machines, I used the copytruncate method to rotate logs. However, I encountered the issue of sparse files. Is it possible that version 3.0 release 0 does not support the copytruncate method yet, and currently only version 2.0 supports it?
|
winlinvip
changed the title
srs 2.0 logrotate copytruncate 产生文件空洞
srs 2.0 logrotate copytruncate generates file holes
Jul 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description'
Please ensure that the markdown structure is maintained.
2.0
Please make sure to maintain the markdown structure.
Reproduction (Replay)
Please make sure to maintain the markdown structure.
Refer to fix
refer
https://blog.csdn.net/caomiao2006/article/details/12752359
Expected Behavior
The log file should not have any gaps.
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: