Hey Adi,
Friday, July 06, 2001, 5:06:36 PM, you wrote:
AL> Hi Kevin,
AL> When I tried the pam_ldap authentication method I experienced a 'weird'
AL> phenomena.
AL> When trying to authenticate with a proper username and password I would
AL> get the same 'signaled to death by 11' log message. However, if I used an
AL> improper password first and the re-tried with a proper password I was able
AL> to connect just fine.
Hmm . . . same thing here. Aggravating.
AL> I've since given up (lack of my debugging knowledge) and switched to the
AL> ldap_mysql patch. I am still interested in the solution of this problem,
AL> though.
Did you patch the patch to allow uids to be anywhere, and not all in the
same rdn? If so, want to send it over? Otherwise, I'll be coding this
myself if anyone's interested. Unless of course, this problem, whatever it
may be, is resolved first.
AL> Regards,
AL> Adi Linden
AL> On Fri, 6 Jul 2001, Kevin J. Menard, Jr. wrote:
>> But the time it worked, I had a line for "reading symbols from
>> /lib/security/pam_ldap". And in my /var/log/imapd.log, I have:
>>
>> Jul 6 09:26:53 balthasar imapd[559]: pam_ldap: error trying to bind as user
>"uid=cyradm,
>> ou=Admins, o=negativetwenty" (Invalid credentials)
>> Jul 6 09:27:06 balthasar imapd[559]: accepted connection
>> Jul 6 09:27:50 balthasar imapd[559]: login: localhost[127.0.0.1] cyradm plaintext
>>
>> (I logged in wrong the first time.)
>>
>> Whereas, I typically have:
>>
>> Jul 6 09:48:47 balthasar master[470]: about to exec /usr/cyrus/bin/imapd
>> Jul 6 09:48:47 balthasar service-imap[470]: executed
>> Jul 6 09:48:47 balthasar imapd[470]: accepted connection
>> Jul 6 09:48:49 balthasar master[454]: process 470 exited, signaled to death by 11
--
Kevin
