Bug#932253: /usr/lib/dovecot/maildirlock does complains about no timeout given (although I did give it one)

2019-07-17 Thread Timo Sirainen
On 17 Jul 2019, at 4.52, Jeronimo Pellegrini wrote: > > $ /usr/lib/dovecot/maildirlock PATH_TO_MAILDIR 100 > Panic: BUG: No IOs or timeouts set. Not waiting for infinity. We recently added code to make sure Dovecot never just waits infinitely when nothing can wake it up. Looks like there's the

Bug#932253: /usr/lib/dovecot/maildirlock does complains about no timeout given (although I did give it one)

2019-07-16 Thread Jeronimo Pellegrini
Package: dovecot-core Version: 1:2.3.4.1-5 Severity: normal Tags: upstream Hello, After upgrading a server to buster, dovecot was upgraded to 1:2.3.4.1-5, and /usr/lib/dovecot/maildirlock now complains that it did not get a timeout parameter (although I did pass the argument). How to reproduce: