[Samba] winbind and AD password updates

[Pierre Ossman]

Guenther Deschner wrote:
> On Mon, May 15, 2006 at 03:49:06PM +0200, Pierre Ossman wrote:
>> More funkyness. Somewhere in pam_winbind (or something it calls), 
>> exit_group(101) gets called, killing of my application. Known issue?
> 
> No, there is no such call in winbindd or pam_winbind.
> 

Doing some gdb:ing, I got this backtrace:

#0  0x4005d146 in exit () from /lib/tls/libc.so.6
#1  0x080488f9 in ?? ()
#2  0x00000065 in ?? ()
#3  0x08048c23 in _IO_stdin_used ()
#4  0x0804e180 in ?? ()
#5  0x0804e180 in ?? ()
#6  0x0804e245 in ?? ()
#7  0x00000003 in ?? ()
#8  0x00000003 in ?? ()
#9  0x4002b8df in pam_get_item () from /lib/libpam.so.0
#10 0x400202d4 in _get_ntstatus_error_string ()
    from /lib/security/pam_winbind.so
#11 0x40020329 in _get_ntstatus_error_string ()
    from /lib/security/pam_winbind.so
#12 0x400203ac in _get_ntstatus_error_string ()
    from /lib/security/pam_winbind.so
#13 0x4002247a in pam_sm_chauthtok () from /lib/security/pam_winbind.so
#14 0x4002cf1a in _pam_dispatch () from /lib/libpam.so.0
#15 0x4002f2a3 in pam_chauthtok () from /lib/libpam.so.0
#16 0x08048aa3 in ?? ()

As libpam is the last offender, I probably should throw the ball their 
way. But could you have a quick look to make sure you're in the clear 
with regard to the samba functions in the backtrace?

-- 
Pierre Ossman                Telephone: +46-13-21 46 00
Cendio AB                    Web: http://www.cendio.com