[Samba] smbcontrol smbd ping also answered by nmbd and winbindd

[Jeremy Allison]

On Tue, Jan 06, 2009 at 02:28:22PM +0100, Michael Weiser wrote:
> Hello,
> 
> with samba-3.0.x an "smbcontrol smbd ping" was answered by all running
> smbd processes. With samba-3.2.x it is now *also* answered by nmbd and
> winbindd:
> 
> [root at cs00 ~]# smbcontrol -V
> Version 3.2.5
> [root at cs00 ~]# for i in `smbcontrol -t 1 winbindd ping | grep PONG | awk
> '{ print $4}'` ; do pstree -p | grep $i ; done
>         winbindd(29908) - winbindd(29909)
> [root at cs00 ~]# for i in `smbcontrol -t 1 nmbd ping | grep PONG | awk '{
> print $4}'` ; do pstree -p | grep $i ; done
>         nmbd(29266)
> 
> [root at cs00 ~]# for i in `smbcontrol -t 1 smbd ping | grep PONG | awk '{
> print $4}'` ; do pstree -p | grep $i ; done
>         smbd(29275)---smbd(29277)
>         winbindd(29908)---winbindd(29909)
>         nmbd(29266)
> 
> (I'm using SerNet RPMs for RHEL4 on an RHEL4u4 machine.)
> 
> With 3.0.30 it looked like this:
> 
> l1-auto-du:~ # smbcontrol -V
> Version 3.0.30-s+c
> l1-auto-du:~ # for i in `smbcontrol -t 1 smbd ping | grep PONG | awk '{
> print $4}'` ; do pstree -p | grep $i ; done
>         |-smbd(4587)-+-smbd(4591)
>         |            |-smbd(5681)
> [...]
>         |            `-smbd(6431)
> 
> Is this known behaviour? What can be done about it?

Yeah - Herb found this problem, see this mail thread :

"http://markmail.org/message/iivngxhc4mwpdi4s#query:herb lewis smbcontrol samba.org+page:1+mid:j5n4r27dnkiciemo+state:results"

for details. This got changed in the 3.3 source tree
(and beyond) but not in the 3.2.x tree.

Jeremy.