RE: SASL authentication

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] 
> Sent: Monday, March 09, 2009 10:36 PM
> To: Xu, Qiang (FXSGSC)
> Cc: Rich Megginson; [email protected]
> Subject: Re: SASL authentication
> 
> 
> do a truss(1) [or similar] on it to see where libsasl looks 
> for its plugins and exactly which plugins its trying to find. 
> libldap does not have any requirements on where those sasl 
> plugins should reside in fact it doesnt know about them at 
> all. it knows sasl mech names and its up to libsasl to map 
> them mech names to its plugins and to take care of locating 
> and loading related plugins. you should also try SASL_PATH 
> trick Rich suggested to you.

Unfortunately, our printer is an embedded system, and the OS in it is a simplied Wind River Linux system. There is no "truss" command available in it. Even the command "env" is not available. So I don't know how to set this SASL_PATH into the environment. 

However, when I use "ldd" to the library, it displays:
====================================
mbc80:/opt/nc/lib <207> ldd libsasl2.so
        linux-gate.so.1 =>  (0xffffe000)
        libdl.so.2 => /lib/libdl.so.2 (0xb7eed000)
        libresolv.so.2 => /lib/libresolv.so.2 (0xb7edb000)
        libc.so.6 => /lib/libc.so.6 (0xb7dca000)
        /lib/ld-linux.so.2 (0x80000000)
====================================
Shouldn't the libraries for plugins also appear in the list?

Thanks,
Xu Qiang