Hi Ceki. The system property approach to this may fit our requirements. I'll have a closer look.
Thanks /Thorbjørn -----Original Message----- From: logback-user-boun...@qos.ch [mailto:logback-user-boun...@qos.ch] On Behalf Of ceki Sent: 13. august 2012 18:25 To: logback users list Subject: Re: [logback-user] Making logging failures fatal. Hi Thorbjørn, Have you considered writing a custom status listener [1]? [1] http://logback.qos.ch/manual/configuration.html#statusListener On 09.08.2012 13:43, Thorbjørn Ravn Andersen wrote: > I need to make logback report problems back as exceptions. > > Our general deployment scenario is one where programs are restarted > every day, and are tedious to monitor unless they explicitly make > themselves heard. Hence logfiles are important and a failure in the > logging framework configuration should cause the program to stop there > and then. > > To my knowledge things like cannot write to log file X/Y/Z or bad > configuration are currently just logged using logbacks internal > mechanism and the application does not know anything about it. > > Id prefer not having logback specific code in my application as we > strive to be logging framework neutral, but if it is unavoidable to do > this I can make an exception. > > Thanks for any help > > /Thorbjørn > > -- Ceki http://tinyurl.com/proLogback _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user
