Skip to content
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

Apply max_log_file constraint when timestamp_in_log_file=false #1089

Open
andrembcosta opened this issue Mar 19, 2024 · 0 comments
Open

Apply max_log_file constraint when timestamp_in_log_file=false #1089

andrembcosta opened this issue Mar 19, 2024 · 0 comments

Comments

@andrembcosta
Copy link

Currently, when the flag timestamp_in_log_file=false and max_log_file is set, instead of quitting logging or overwriting to preserve the size limit, glog just appends to the log file and eventually breaks the size limit.

Am I missing another flag to get the intended behavior of having a single log file of limited size? Or is this an actual limitation?

This appears to be similar to #809

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant