Re: SASL2 plugin problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Looks like strace and SystemTap are Linux equivalents.

Try the SASL utility first, but remember that applications (like LDAP) can override the default plugin directory. If that happens the system trace capability is your best bet.

On Mar 10, 2009, at 9:09 PM, Xu, Qiang (FXSGSC) wrote:

-----Original Message-----
From: Henry B. Hotz [mailto:hotz@xxxxxxxxxxxx]
Sent: Wednesday, March 11, 2009 12:01 PM
To: Xu, Qiang (FXSGSC)
Cc: cyrus-sasl@xxxxxxxxxxxxxxxxxxxx
Subject: Re: SASL2 plugin problem

Something like ktrace or dtrace to make the kernel tell you
what files it's trying to open will usually help.

But ktrace and dtrace is a utility in Unix/FreeBSD/MacOS. The OS in our printer is Wind River Linux, and this utility is not available.

Is there any tool in Cyrus release itself that can be used to check which plugin libsasl2.so is looking for?

Thanks,
Xu Qiang

------------------------------------------------------
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz@xxxxxxxxxxxx, or hbhotz@xxxxxxx




[Index of Archives]     [Info Cyrus]     [Squirrel Mail]     [Linux Media]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux