background: I had a stock redhat samba setup using security = share and sharing out three directories - [homes] and two fixed locations. pretty trivial setup. I built Samba 3 head (current as of this morning, but the problem has been happening for at least a week) and tried connecting to it from a NT4 PDC with a different domain name to the samba server, and I get a segv. Debug level 10 doesn't give me a whole lot to go on, so I ran smbd under gdb instead:
pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0 Program received signal SIGSEGV, Segmentation fault. 0x080952c6 in reply_sesssetup_and_X (conn=0x0, inbuf=0x403b2008 "", outbuf=0x403d3008 "", length=266, bufsize=131072) at smbd/sesssetup.c:721 721 if (server_info->guest) { stacktrace: #0 0x080952c6 in reply_sesssetup_and_X (conn=0x0, inbuf=0x403b2008 "", outbuf=0x403d3008 "", length=266, bufsize=131072) at smbd/sesssetup.c:721 #1 0x080ae095 in switch_message (type=115, inbuf=0x403b2008 "", outbuf=0x403d3008 "", size=266, bufsize=131072) at smbd/process.c:758 #2 0x080ae121 in construct_reply (inbuf=0x403b2008 "", outbuf=0x403d3008 "", size=266, bufsize=131072) at smbd/process.c:788 #3 0x080ae431 in process_smb (inbuf=0x403b2008 "", outbuf=0x403d3008 "") at smbd/process.c:889 #4 0x080aedfa in smbd_process () at smbd/process.c:1298 #5 0x080731d4 in main (argc=6, argv=0xbfffe044) at smbd/server.c:907 #6 0x401e21c4 in __libc_start_main () from /lib/libc.so.6 Regardless of whether this turns out to be a misconfig on my part, a panic is the wrong way to go about handling it. Especially since this is just an upgrade from samba 2 to samba 3. Cheers, Waider. -- [EMAIL PROTECTED] / Yes, it /is/ very personal of me. "They posted while drunk, their souls are forfeit." - Bren, in the dspsrv orientation guide.