Good afternoon,
We are using Logback in a security sensitive application.
The logging configuration normally includes a RollingFileAppender but we
have the following requirement: If at any time a write to the log fails
(due to a full disk, file permissions, etc.) the application must halt
immediately, because no logs means no audit data, and that constitutes a
high security risk.
Now, the usual behavior when Logback can't write to the file is to log the
error and continue. What would be the right way to handle this?
Thank you,
Gabriel
