-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[Feature] Provide a configuration option for logs rotation #114
Comments
Hello, any update on this? Any way to disable that log splitting so I'll handle logs myself with logrotate? |
Ping @guagualvcha |
hi @gituser this make sense. Noted. |
We have responded to the question and will proceed to close the case as we didn't get any additional question after 3days. Please proceed to join our Discord channel for more discussion at https://discord.com/invite/YPDsUqcwR8 |
@BinanceG11 Why do you close this? This is a feature request and it has been accepted by @guagualvcha |
Noted. @gituser reopen. Apologies |
@vnermolaev can we add a |
@gituser we have merged the changes to be able to modify the log rotation duration. |
hey @bnb-tw unfortunately with bsc v1.2.10 it didn't work for me. I've set in my
But I still see that there is a new file being created every hour:
|
Ping @vnermolaev @bnb-tw @alexlucaci |
will be in next release: v1.3.6 |
@gituser with v1.3.6
|
Co-authored-by: will@2012 <xibaow2020@qq.com>
System information
Geth version: 1.0.6
OS & Version: Linux
Commit hash : latest release
Expected behaviour
Currently, geth creates every hour a new log file even if you set the
MaxBytesSize
to relatively large value (e.g. 100MB), e.g.:This results in:
It seems there is no option to disable logs rotation by hour in the configuration file.
So would be nice to add an option into the config file to:
Of course, you could completely disable
[Node.LogConfig]
section and log into stdout and then handle the logs by yourself, but it's not practical, it will involve more tooling.The text was updated successfully, but these errors were encountered: