On Tue, Oct 4, 2011 at 10:28 AM, Henrique de Moraes Holschuh
h...@debian.org wrote:
On Tue, 04 Oct 2011, Ondřej Surý wrote:
I agree on fixing SIGQUIT behaviour.
Does anyone have an easy way to test whether sigquit is doing the right
thing on open but idle connections of the various protocols?
I've attached two patches.
The first once changes grep to exclude the *_path options in
lib/imapoptions. This ensures cyrus-db-types.txt is generated correctly.
Next, cyrus-common-2.4.postinst was only setting RET if upgrade-db
failed. So RET was null in the case statement, triggering the
Package: cyrus-imapd-2.4
Version: 2.4.9~beta1-1
Severity: normal
Tags: patch
Per the documentation for 2.4, the locks should be cleaned out. I think
cleaning out proc
at the same time would be a good idea, in case a file is left after a crash.
As well in the init script I:
* Silenced
On 11-05-20 06:45 AM, Ondřej Surý wrote:
Hi Steven,
could you try attached init.d script?
I made some minor corrections.
* Silenced pidofproc in do_start and try-restart
* Fix pidofproc return code handling in do_stop (otherwise
/etc/init.d/cyrus-imapd stop always returned failed)
I'll
Package: cyrus-common-2.4
Version: 2.4.8-7
install-configure.html says we should use QUIT first:
Since a clean shutdown may never finish if a child process is stuck
for some reason the recommended approach is to send a SIGQUIT then loop
on the master process sending a signal 0 every second
Package: cyrus-replication-2.4
Version: 2.4.8-7
I'm testing cyrus 2.4.8 to upgrade our cyrus deployment. On various
mailboxes sync_client exits with the error:
Fatal error: Internal error: assertion failed: seen_db.c: 127:
*seendbptr == NULL
I can reproduce this error consistently by doing
