Hi there.
I have just installed DOVECOT 1.0.1 for the first time.
After launching it, I can verify that
ps -ax | grep -i dovecot
1052 ?? Ss 0:00.03 /usr/local/dovecot/sbin/dovecot -c
/etc/dovecot/dovecot.conf
1053 ?? S 0:00.06 dovecot-auth
1058 p2 R+ 0:00.01 grep -i dovecot
As you're getting SIGILL, have you verified that your dovecot (and all
libraries it depends on) has been compiled for the right target CPU?
Greetings,
Gunter
As far as I can tell, yes.
Checking in the DOVECOT build's config.log
ac_cv_build=powerpc-apple-darwin8.9.0
ac_cv_host=powerpc-app
In the x86 world you'll get SIGILL if you try to run Pentium M compiled
code on a 586 platform, or SSE/MMX enabled code on a CPU which does not
support these extended instruction sets.
I don't know about PPCs, though.
I've read about such troubles on the PPC, but it looks like you have to
s
After noticing a commit to the HG repository,
http://hg.dovecot.org/dovecot-1.0/rev/f88b1e225be5
about,
" We didn't update last_output timestamp with long fetches,
causing Dovecot to idle-disconnect the client."
I chekced out the latest from the DOVECOT-1.0 repo, and built again.
Unfo
Hi Timo,
Thanks for the instruction as to how to debug this.
You could try running imap manually with gdb:
gdb /usr/local/libexec/dovecot/imap
r
I've not used gdb before. Reading MAN page, and some instructions online, I
tried to launch as you had instructed, but it died off.
gdb -
So it's not dying at least at startup. Maybe an easier way would be to
make the process dump core and gdb the core file. See
http://dovecot.org/bugreport.html#coredumps
I'm still not clear how one gets gdb to exec 'imap' WITH the config file.
Instead, by selectively disabling items in my dove
