Hi,
> On Thu, 20 Dec 2007 13:17:37 +0100
> Gilles Bruno <[EMAIL PROTECTED]> said:
Gilles.Bruno> there was also an issue with bsd getgroup functions some time ago
(iirc
Gilles.Bruno> it was during the 2.3.10 release). Did you try adding this simple
line :
Gilles.Bruno> unix_group_enabl
Hi John,
there was also an issue with bsd getgroup functions some time ago (iirc
it was during the 2.3.10 release). Did you try adding this simple line :
unix_group_enable: 0
to your imapd.conf and give it a try ?
I hope it's not totally of topic, but a stock compile of cyrus 2.3.10+
on a Free
Sebastian Hagedorn wrote, On 12/19/2007 4:10 AM:
>
> I'm only guessing here, but based on similar issues I had with (other)
> libraries it's perhaps a conflict in Berkeley versions. Is it possible
> that cyrus-imapd and cyrus-sasl were compiled/linked against different
> versions?
>
>
Yes
--On 19. Dezember 2007 02:04:57 -0500 John Crawford
<[EMAIL PROTECTED]> wrote:
Well, I did a gdb run for the first time with cyrus, using the
debug_command option in imapd.conf (and CFLAGS="--debug -g -Wall")
for cyrus-imap23's work directory.
Here's the first bits of the traceback for my "im
hi.
Well, I did a gdb run for the first time with cyrus, using the
debug_command option in imapd.conf (and CFLAGS="--debug -g -Wall")
for cyrus-imap23's work directory.
Here's the first bits of the traceback for my "imtest" invoked blowup
(no debugging symbols found)...(no debugging symbols foun
Hi John!
I had just the identical problem last night, but I was able to trace it
down to a bug in the ldapdb auxprop module. You are not using that
module, so that can't be it.
How would one do an strace on imapd to find out in what function call it
dies? That might be an indication.
Regards,
