On Aug 4, 2008, at 3:04 PM, Kyle Wheeler wrote:
The issue, I think, is that maildirlock has a race condition. There
is no guarantee that the parent has set up its signal handlers
before the child gets around to killing it.
Oh, you're right.
I think signals are probably a bad way of handlin
On Monday, August 4 at 01:54 PM, quoth Timo Sirainen:
On Thursday, July 24 at 03:05 AM, quoth Timo Sirainen:
+ Added a new maildirlock utility for write-locking Dovecot
Maildir.
Every time I attempt to use this (as root), it exits with a return code
of 143 and my shell prints out "Termina
On Jul 24, 2008, at 3:28 PM, Kyle Wheeler wrote:
On Thursday, July 24 at 03:05 AM, quoth Timo Sirainen:
+ Added a new maildirlock utility for write-locking Dovecot
Maildir.
Every time I attempt to use this (as root), it exits with a return
code of 143 and my shell prints out "Terminated"
On Jul 27, 2008, at 12:41 PM, Ralf Hildebrandt wrote:
* Bruce Bodger <[EMAIL PROTECTED]>:
Timo,
Is this safe to install? The reason that I ask, I read a few
reports of
problems immediately after your announcement and haven't seen your
responses to them.
It's giving me less odd warnings
* Bruce Bodger <[EMAIL PROTECTED]>:
> Timo,
>
> Is this safe to install? The reason that I ask, I read a few reports of
> problems immediately after your announcement and haven't seen your
> responses to them.
It's giving me less odd warnings in the log than 1.1.1 :)
Count that as a "yes".
--
Timo Sirainen wrote:
> http://dovecot.org/releases/1.1/dovecot-1.1.2.tar.gz
> http://dovecot.org/releases/1.1/dovecot-1.1.2.tar.gz.sig
>
I (finally) refreshed the managesieve patch to cleanly apply on the new
release:
http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.2-managesieve-0.10.3.diff.gz
On Thursday, July 24 at 03:05 AM, quoth Timo Sirainen:
+ Added a new maildirlock utility for write-locking Dovecot
Maildir.
Every time I attempt to use this (as root), it exits with a return
code of 143 and my shell prints out "Terminated".
I'm guessing that what happens is a result of thi
