Scott Russell wrote:
>
> All -
>
> I'm new to Cyrus and have been experiencing sig 11 issues on imapd over the
> past 2 weeks. I've spent a great deal of time reading the list archives
> trying to id the root cause. So far it hasn't been pretty but I've boiled
> down to the following info.
[...]
> Conclusion:
>
> Something introduced into imapd.c between 2.0.13 and 2.0.14 is causing imapd
> to sig 11 on Red Hat 6.2 (And possibly Red Hat 7.1). A diff between the two
> files shows several changes but I don't have enough experience to spot the
> root cause. No core files are generated when a sig 11 happens so a gdb trace
> isn't available.
>
> If anyone wants to provide me with a patch against imapd for 2.0.14 that I
> can test I'll be happy to do it and report the results.
Scott,
Please try this patch.
Ken
Index: imapd.c
===================================================================
RCS file: /afs/andrew/system/cvs/src/cyrus/imap/imapd.c,v
retrieving revision 1.308
diff -c -r1.308 imapd.c
*** imapd.c 2001/06/23 03:14:02 1.308
--- imapd.c 2001/07/05 19:09:03
***************
*** 1526,1531 ****
--- 1526,1533 ----
int *ssfp;
char *ssfmsg=NULL;
+ char *canon_user;
+
sasl_result = sasl_server_start(imapd_saslconn, authtype,
NULL, 0,
&serverout, &serveroutlen,
***************
*** 1589,1595 ****
* mysasl_authproc()
*/
sasl_result = sasl_getprop(imapd_saslconn, SASL_USERNAME,
! (void **) &imapd_userid);
if (sasl_result != SASL_OK) {
prot_printf(imapd_out, "%s NO weird SASL error %d
SASL_USERNAME\r\n",
tag, sasl_result);
--- 1591,1598 ----
* mysasl_authproc()
*/
sasl_result = sasl_getprop(imapd_saslconn, SASL_USERNAME,
! (void **) &canon_user);
! imapd_userid = xstrdup(canon_user);
if (sasl_result != SASL_OK) {
prot_printf(imapd_out, "%s NO weird SASL error %d
SASL_USERNAME\r\n",
tag, sasl_result);
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
