On 10/08/06, dale gallagher wrote:
On 10/08/06, Timo Sirainen wrote:
On Thu, 2006-08-10 at 17:29 +0200, dale gallagher wrote:
I'm now getting the following error in the logs - any idea? The error isn't terribly informative.
Fatal: sigaction(SIGRTMIN) failed: Invalid argument
configure --with-ioloop=none
I'll fix this anyway in next version to just silently not use dnotify.
I tried building with --with-ioloop=none alone, but that resulted in the same error, namely: Fatal: sigaction(SIGRTMIN) failed: Invalid argument
Then, I configured with both --with-ioloop=none and --with-notify=none and the original error has gone, but a new one has reared its head:
dovecot: Info: Dovecot v1.0.rc6 starting up dovecot: Error: Login process died too early - shutting down dovecot: Error: child 17320 (login) killed with signal 11 dovecot: Error: child 17319 (login) killed with signal 11
Where should I look for problems now? Could this be with my checkpassword binary?
I've tried various settings for the dovecot (login) user, without any change in the above errors.
Attempt 1: HOME=/bin/true, SHELL=/bin/true Attempt 2: HOME=/var/log/dovecot/login, SHELL=/bin/sh
Am I barking up the wrong tree with trying to tweak the login user's env?
Any ideas?