In wbclient.c the call that causes signal 11 is the call to initgroups
in the winbind_initgroups function.
-----Original Message-----
First off, we are forced to using said versions and NIS+, so no flaming on
those issues please.
Also, the samba version we recieved was forced upon us and we are not
allowed to recompile,
however in a test environment we've compiled both with and without NIS+
support and the same
errors are generated.
When removing nisplus from group entry of nsswitch.conf samba works fine.
With nisplus
listed in nsswitch.conf group entry, the forked smbd process dies when
attemping to connect
with either a Windows machine or smbclient. Here is the error from the
smbclient connection
attempt:
session setup failed: Call returned zero bytes (EOF)
(truss output)
incurred fault #6, FLTBOUNDS %pc = 0xEF5DA2B0
siginfo: SIGSEGV SEGV_MAPERR addr=0x0084D62C
Recieved signal #11, SIGSEGV [caught]
siginfo: SIGSEGV SEGV_MAPERR addr=0x0084D62C
from debug level 10
smbd/sec_ctx.c:set_sec_ctx(329)
setting sec ctx (0, 0) - sec_ctx_stack_ndx =1
lib/fault.c:fault_report(38)
smb.conf setup
[global]
workgroup = workgroup
security = SERVER
encrypt passwords = Yes
password server = pserver
Thanks for any helpful information. Preferred solution is to be able to use
nisplus listed in groups
entry of nsswitch.conf.
Rob
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
