-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
will log4rs support file size control and rolling file ? #8
Comments
Yep, appender configuration's pretty rudimentary right now, but log rotation is definitely something I want to add. |
I like this lib. But log rotation is a rigid requirement for me. Maybe I should not ask , but I really want to know is this requirement in schedule already? |
It's part of some expansion I have been meaning to do. I'll hack on it over the weekend. |
That's great,I am looking forward to it |
Now that log4rs 0.4 is released, I'm going to start tackling this. I think I'll probably work on it in a separate repo/crate initially until the API gets worked out, but then move it in since it's such a core concept. |
While you're thinking about the API, it would be nice to support external rotation utilities like |
I was planning on having a similar setup to Logback, where there's a "triggering policy" that decides when the log should roll, and a "rotation policy" that decides what to do at that point. I think it should be possible to write a triggering policy that the logback postrotate command can poke, and a rotation policy that just closes and reopens the file. |
That sounds great! |
I'm working on this here: https://github.com/sfackler/log4rs-rolling-file Not quite ready for a release yet, but the basics are there. |
This is now on crates.io: https://crates.io/crates/log4rs-rolling-file It's still missing some functionality like TimeBasedRollingPolicy which is a bit weird from an API perspective but probably the most common policy people actually use, so I'm going to keep it in a separate crate for now until that gets worked out. |
No description provided.
The text was updated successfully, but these errors were encountered: