I would suggest that you cover this in the documentation for prudent mode. In fact, my recommendation would be to add something like "File locking is known to have issues on networked file systems and on various operating systems. As such, Logback (or any other application) cannot guarantee the deadlocks and file corruption will not occur and any issues reported in this area must be able to show that the problem is due to Logback, not the underlying OS or file system. Instead, it is recommended that applications be designed to write to log files from a single process within the environment".