Well, I don't think it matter. Although I'm not sure that I've
configured backend properly and I don't know if one backend excludes
the others (i.e. they may be loaded anyway).
I've tried with three different backend (not at the same time):
plugin {
quota = fs:user
}
plugin {
quota = dirsize:user
quota_rule = *:storage=1024M
}
plugin {
quota = maildir:storage=10240:ignore=Trash
}
All three variants gives me the same behaviour.
/Magnus
12 dec 2008 kl. 16.13 skrev Timo Sirainen:
On Dec 12, 2008, at 5:06 PM, Magnus Appelquist wrote:
After a couple of seconds when I try to start dovceot, I get this:
r...@taleira:~# /etc/init.d/dovecot start
Alarm clock
If I uncomment the "imap_quota and quota" in dovecot.conf
everything seem to work fine
What quota backend are you using? fs or maildir?
wait4(-1, 0xffbd7e9c, 0, NULL) = ? ERESTARTSYS (To be
restarted)
--- SIGALRM (Alarm clock) @ 0 (0) ---
+++ killed by SIGALRM +++
Dovecot doesn't have any calls to send SIGALRM signals.. If you're
using fs quota with NFS rpc calls, that could cause it I guess,
although I don't really understand why the signal would be sent to
master process instead of just the child process.
