Hi Peter,
Take a look at your Makefile, and see if the following line looks correct:
WINBIND_NSS_OBJ = nsswitch/winbind_nss.o nsswitch/wb_common.o
nsswitch/winbind_nss_solaris.o
If it JUST has:
WINBIND_NSS_OBJ = nsswitch/winbind_nss.o nsswitch/wb_common.o
this could be your problem...
Another thing to look for, are the files nss_common.h and nss_dbdefs.h
accessible on your system?
If you can't make progress from this (I don't have a solaris system to
play
with, unfortunately), send me your source/include/config.h,
and your Makefile, and let me take a peek.
Hope this helps,
Don
-----Original Message-----
From: Peter Zahn [mailto:Peter.Zahn@bmw.de]
Sent: Thursday, January 17, 2002 1:57 PM
To: samba@samba.org
Subject: winbindd and solaris?
-----BEGIN PGP SIGNED MESSAGE-----
Dear Samba team,
scanning the samba docu and web/newsgroups, I was not sure whether
currently sambas (V2.2.0) winbindd would work on solaris (I
use solaris release level 5.7 at the moment).
I tried it out and found that winbindd did compile & run and
could properly authenticate users in domain security mode (the log
contained proper confirmations).
Nevertheless I could not "login"/"rlogin", and it looks like
the reason is
that the "winbind" callback in "nsswitch.conf" is broken and
the /usr/security/pam_winbind.so shared library is not called. When I
looked at the symbols in pam_winbind.so, it looks that they define not what
the solaris "nscd" ("name service cache daemon" which
operates the
nsswitch.conf
file and the shared libraries called for name service) expects to be
defined.
My Question: is this analysis correct and is there no way to make winbindd
operate on solaris (in this case: is some development in process?), or is it
possible to make it functionable in some manner?
It would be great if somebody could give me a hint!
Thanks a lot,
Peter Zahn
=Dr. Peter Zahn, BMW AG, EV-25, D-80788 Munich
Phone: +49-89-382-45003 e-mail: Peter.Zahn@bmw.de
Fax: +49-89-382-70-45003 Intranet: http://forschung.muc/Zahn
-----BEGIN PGP SIGNATURE-----
Version: PGP for Business Security 5.5.3
Comment: BMW AG; BMW InformationsSicherheit; PGP-Policy 1.1
iQEVAwUBPEcQYBG4ObjwNNBTAQEUIAf9GwcDuUt61A3VEXU5telBvB1N0OQ2W2gj
i3BkjJ8+MInSfZcj+VBMAVjHbqkJLFr0gQQnLe8ZnHe/UUDhBVb18bV9z1MNnH8b
zMNOuk2O5NEvFM/n5CXksaaOfjEt+kfy2GdbtbP/bq/Aqn2ym6+vTHu+P9FiinKu
apafgaiiUdjSh+r/ixj/FsLoN7NlILk3bvUqN+os5fKfUobU53Lto2bGzx/q0OAx
LfDAAnMUOpHow7txHtq6FRNkWl9GaPH/woQew4iDU0rjAIkg+oOVMVO5Ru+TQnss
mOywRdLWjbjqoKWvsd5iz82mwbn5RFpTueNv+e4eJUS61p1agjWlVw==LYP8
-----END PGP SIGNATURE-----