Winbind problem or my problem:)
Osman Tufanogullari (Garanti Teknoloji)
OsmanTuf at garanti.com.tr
Thu Jun 20 08:56:03 GMT 2002
I did what you said and here is output...
#0 0x420b4769 in wait4 () from /lib/i686/libc.so.6
#1 0x4213030c in __DTOR_END__ () from /lib/i686/libc.so.6
#2 0x42049f72 in system () from /lib/i686/libc.so.6
#3 0x0808d895 in smb_panic ()
#4 0x0807d960 in fault_report ()
#5 0x0807d9ae in sig_fault ()
#6 <signal handler called>
#7 0x0806d7c4 in query_user ()
#8 0x08069b22 in query_user ()
#9 0x0806494d in winbindd_getpwnam ()
#10 0x080638b7 in process_request ()
#11 0x08063b06 in process_packet ()
#12 0x0806406e in process_loop ()
#13 0x08064579 in main ()
#14 0x42017499 in __libc_start_main () from /lib/i686/libc.so.6
From: Esh, Andrew [mailto:AEsh at tricord.com]
Sent: Thursday, June 20, 2002 5:29 PM
To: Osman Tufanogullari (Garanti Teknoloji); samba-technical at lists.samba.org
Subject: RE: Winbind problem or my problem:)
The "panic action" smb.conf parameter can be used to display a debugger when the code panics. On Linux, I use this:
panic action = "gnome-terminal --command 'gdb /proc/%d/exe %d'"
This will open a new terminal window and display the gdb debugger, positioned at the point of the panic. Doing a "bt" at that point will show what code was running when it panicked.
We need that information in order to deal with this problem.
From: Osman Tufanogullari (Garanti Teknoloji) [ mailto:OsmanTuf at garanti.com.tr]
Sent: Thursday, June 20, 2002 5:02 AM
To: samba-technical at lists.samba.org
Subject: Winbind problem or my problem:)
Did you have a problem with winbindd which got all the users from the domains except its own domain!?
when you reach a share on samba with its own domain user, Signal 11 is received and kills itself...
Winbindd can bind the PDC of its own domain like it does for the trusted ones but it doesnt get the user or groups of only its domain...
-------------- next part --------------
HTML attachment scrubbed and removed
More information about the samba-technical