winbindd client connection status in 3.0.25

[Herb Lewis]

The feature hasn't been dropped just the info is printed
wrong. We now always print PID 0 instead of actual PID of the
winbindd client. Seems like we lost an initialization of the
value somewhere but I cannot see where it should have been done.
Sending a SIGUSR2 on 3.0.8 did produce valid PIDs (except for
the first one)

3.0.8 log output at debug level 2 after SUGUSR2

winbindd status:
         2 clients currently active
         client list:
                 pid 0, sock 20, rbl 0, wbl 0
                 pid 4934, sock 23, rbl 0, wbl 0

3.0.25 log output

winbindd status:
         4 clients currently active
         client list:
                 pid 0, sock 22
                 pid 0, sock 26
                 pid 0, sock 25
                 pid 0, sock 20


Gerald (Jerry) Carter wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Herb Lewis wrote:
> 
>>winbindd is supposed to print out client connection status on
>>a USR2 signal. If debuglevel is set at 2 it lists all the PIDs
>>as 0 instead of the actual PID. Not quite sure where to look
>>for where this went wrong. It used to work. 3.0.8 was the
>>last time I looked at this.
> 
> 
> No idea Herb.  I don't remember any discussion about dropping
> that feature.  But then again, neither did I even know it
> existed.
> 
> 
> 
> 
> cheers, jerry
> =====================================================================
> Samba                                    ------- http://www.samba.org
> Centeris                         -----------  http://www.centeris.com
> "What man is a man who does not make the world better?"      --Balian
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFGXJNxIR7qMdg1EfYRAv0LAKCKNIV+6ykxkChnWG0DJ0f4OTOZUwCg7+WA
> 7YNI8a3TdD00OBmb+ZG9Tds=
> =zcrR
> -----END PGP SIGNATURE-----