Hmm, I have rolled my own roll-on-startup policy but that is not, as
written compatible with a roll-by-day setup, as it uses different file
naming conventions. I use it for personal debugging but not in
production. I'm not sure it's possible to combine the two in a single
policy, if in fact, the default time-based policy does NOT roll on
startup the app wasn't running at the boundary crossing.
Can I get a definitive answer on whether the default time-based policy
will roll on startup if the application wasn't running at the boundary
crossing?
On 06/05/2013 12:59 PM, David Roussel wrote:
Have you looked at the changes since 1.0.7 to see if any apply?
Lack of rolling is curtly a difficult one to debug. Best way is to
configure one roll per minute or more often and do a soak test.
Roll at startup is discussed here.
http://stackoverflow.com/questions/2492022/how-to-roll-the-log-file-on-startup-in-logback
David
On 5 Jun 2013, at 18:46, Steve Cohen <[email protected]
<mailto:[email protected]>> wrote:
On 06/05/2013 12:35 PM, Robert Kuhar wrote:
Also, if your app isn't running when the trigger is me, it is my
understanding and observation that the logs won't roll.
"When the trigger is me"? What does this mean? I had thought that
the rollover would happen whenever the day (in my case) crossed the
boundary from the last entry. But that could easily be wrong.
_______________________________________________
Logback-user mailing list
[email protected] <mailto:[email protected]>
http://mailman.qos.ch/mailman/listinfo/logback-user
_______________________________________________
Logback-user mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-user
_______________________________________________
Logback-user mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-user
