Re: SASL Trace
I am using gdb on freebsd to trace mysql patch. Its been very helpfull, but only after turning on mysql logs I was able to find the problem. So if you can catch the query sent to ldap, try that. I am ot familiar with ldap though. On Thu, Apr 11, 2002 at 09:09:11PM +0200, Birger Toedtmann wrote: > Tim Pushor schrieb am Thu, Apr 11, 2002 at 09:49:39AM -0600: > > Is there any way to trace what SASL is doing? > > > > I am trying to get simon's ldap auxprop patch working, and it isn't. All I > > am seeing in syslog is > > > > badlogin: localhost[127.0.0.1] plaintext timp SASL(-13): user not found: > > checkpass failed > > > > If I new what SASL was trying to do, I could probably figure out whats > > wrong, but at this point, without any other evidence, I am just grasping at > > straws.. > > If you run it on Linux, you may give an ltrace(1) on the application process > (i.e. imapd) a try. It's very suitable to see whether certain config options > and file paths match and traces the sasl library calls accordingly. > > > Regards, > > Birger > >
Re: SASL Trace
Tim Pushor schrieb am Thu, Apr 11, 2002 at 09:49:39AM -0600: > Is there any way to trace what SASL is doing? > > I am trying to get simon's ldap auxprop patch working, and it isn't. All I > am seeing in syslog is > > badlogin: localhost[127.0.0.1] plaintext timp SASL(-13): user not found: > checkpass failed > > If I new what SASL was trying to do, I could probably figure out whats > wrong, but at this point, without any other evidence, I am just grasping at > straws.. If you run it on Linux, you may give an ltrace(1) on the application process (i.e. imapd) a try. It's very suitable to see whether certain config options and file paths match and traces the sasl library calls accordingly. Regards, Birger
SASL Trace
Is there any way to trace what SASL is doing? I am trying to get simon's ldap auxprop patch working, and it isn't. All I am seeing in syslog is badlogin: localhost[127.0.0.1] plaintext timp SASL(-13): user not found: checkpass failed If I new what SASL was trying to do, I could probably figure out whats wrong, but at this point, without any other evidence, I am just grasping at straws.. Thanks, Tim