Re: SASL2 plugin problem

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

 



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

Xu,

Cyrus provides the 'pluginviewer' utility, which can be used to verify that your gssapi plugin is installed correctly.

If available on your system, ldapsearch might provide an easier way to trouble shoot. 'ldd', or your system's equivalent, should tell you if your ldap library is looking in the correct location for your sasl library, assuming it's dynamically linked.

This might provide some more ideas:

http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/OpenLdapSaslGssapi

- Dan

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

  Powered by Linux