Yes, I did reduce MaxIndex and that indeed made the status messages on stdout go away, sorry, should have mentioned that. I was just wondering how/if it is possible to log this messages elsewhere than stdout.
christian On Mon, Mar 22, 2010 at 3:17 PM, Aleksey Didik <[email protected]> wrote: > Hmm, may be better to reduce MaxIndex to 13? > Logback will reduce it automatically anyway, but if you will make it > yourself, status messages will not be printed. > > Hope this help, > Aleksey. > > 22.03.2010 18:13, Christian Migowski пишет: >> >> Hi Aleksey, >> >> yes it was, thank you! It didn't occur to me that this "small problem" >> leds to automatic status logging, but it makes sense for sure! >> >> Is there a way to "redirect" this output to a logfile? The output to >> stdout confuses my start script and I'd rather have this logback >> warnings written to a file. >> >> thanks again, >> regards, >> christian! >> >> On Mon, Mar 22, 2010 at 3:03 PM, Aleksey Didik >> <[email protected]> wrote: >> >>> >>> Look like the reason is this one: >>> >>> 12:55:20,828 |-WARN in >>> ch.qos.logback.core.rolling.fixedwindowrollingpol...@3a747fa2 - Large >>> window sizes are not allowed. >>> 12:55:20,828 |-WARN in >>> ch.qos.logback.core.rolling.fixedwindowrollingpol...@3a747fa2 - >>> MaxIndex reduced to 13 >>> 12:55:20,832 |-INFO in >>> >>> Aleksey >>> >> >> _______________________________________________ >> Logback-user mailing list >> [email protected] >> http://qos.ch/mailman/listinfo/logback-user >> >> > > _______________________________________________ > Logback-user mailing list > [email protected] > http://qos.ch/mailman/listinfo/logback-user > _______________________________________________ Logback-user mailing list [email protected] http://qos.ch/mailman/listinfo/logback-user
