winbindd question

[Volker Lendecke]

On Wed, Aug 01, 2007 at 03:23:21PM +0530, Aravinda Guzzar wrote:
> >>>The child cases are the equivalent of worker threads.
> Is there a specific reason why "thread" implementation was not used to
> handle different WinBind commands and processes were chosen instead.

Our base libs are not thread safe.

> But few commands like "wbinfo --domain-users  to Lists all domain users" and
> "wbinfo --domain-groups  Lists all domain groups" doesn't create the child
> processes to service the request.
> 
> 1.    My question is how and on what basis is the creation of child process
> is decided. I see that sometimes upto 5 child processes getting created when
> I execute few wbinfo commands and connect to samba which is configured as
> Member Server to windows PDC.

Amount of work vs benefit. Getting user enumeration async
with the architecture we have is pretty hard, and as this is
not executed in any of the hot code paths, it was not yet
seen as pressing enough. No technical reason.

> 2.    If the child process is created when does it get terminated? Currently
> I see that even after processing the command the child processes continues
> to stay there.

It's never terminated. If it dies for some reason, it's
restarted.

> 3.    There is a loop in the below code chain which I couldn't understand
> from the code study/experiments. Can anyone help me in understanding this.
>     init_child_connection() -> async_domain_request() ->
> init_child_connection()

Both are to different children. The first
init_child_connection is to a trusted DC, the second one is
asking "our" DC for a DC name of the trusted domain in case
we don't have a connection yet.

Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20070801/12b5d598/attachment.bin