32-bit and 64-bit nss_winbind.so on Solaris 10

David Collier-Brown David.Collier-Brown at Sun.COM
Tue Oct 25 11:53:46 GMT 2005

  Some solaris applications (appcert, for one), start as
a 32-bit app, and test to see if the thing they're manipulating
is 64-bit. If so they exec the 64-bit instance of themselves
with the same parameters.
  This might do the job for getent on any OS that supports
multiple forms of binary.


Maximilian Kolmhuber wrote:
> I've successfully compiled 32-bit and 64-bit executables of 
> Samba-3.0.20b on my Solaris 10 box.
> I plan to use winbindd to allow Windows AD users to log on my Solaris 10 
> box.
> For testing, I've compiled a 64-bit version of the "getent" utility from 
> the sources available from opensolaris.org since the getent utility that 
> ships with Solaris 10 is only a 32-bit executable.
> Unfortunately, when I'm running the 32-bit Samba, only the 32-bit getent 
> can see the Windows users, and when I'm running the 64-bit Samba, only 
> the 64-bit getent can see them.
> The 32-bit and the 64-bit Samba live in different directory trees.
> Simply using the 32-bit nss_winbind.so with the 64-bit Samba doesn't 
> work, and using the 64-bit nss_winbind.so with the 32-bit Samba doesn't 
> work either.
> Running a 32-bit winbindd and a 64-bit winbindd simultaneously also 
> doesn't solve the problem (overlap in /tmp/.winbindd/pipe ?).
> Any ideas how I could get this to work?
> Thanks in advance!
> Maximilian Kolmhuber
> mk at digitalventure dot de

David Collier-Brown,      | Always do right. This will gratify
Sun Microsystems, Toronto | some people and astonish the rest
davecb at canada.sun.com     |                      -- Mark Twain
(416) 263-5733 (x65733)   |

More information about the samba-technical mailing list