samba - Apr 2005 - winbind on a domain with 150000 users

I am trying to use winbind on a domain with 150000 users, but I can't
make it work. Is that because I have done something wrong, or doesn't
winbind scale to that many users?

It works a little, I can use wbinfo to translate between sid, uid and
gid, and I can also get the groups a user is in. But when I try to get
the list of all users with 'wbinfo -u', I get a timeout and winbindd
starts to eat memory until it gets killed by the oom killer.

I am using samba 3.0.11, there are uids and gids enough
(100000-399999) and I have checked that the kernel supports 32 bit
uids.

-- 
Kim Hansen

Hello,

Kim Hansen wrote:
>I am trying to use winbind on a domain with 150000 users, but I can't
>make it work. Is that because I have done something wrong, or doesn't
>winbind scale to that many users?
>It works a little, I can use wbinfo to translate between sid, uid and
>gid, and I can also get the groups a user is in. But when I try to get
>the list of all users with 'wbinfo -u', I get a timeout and winbindd
>starts to eat memory until it gets killed by the oom killer.
>
>I am using samba 3.0.11, there are uids and gids enough
>(100000-399999) and I have checked that the kernel supports 32 bit
>uids.
>
>  
>
The winbind startup with that many users takes loong, but
that is fixed in 3.0.13.  We observed the same memory
leak in winbind in version 3.0.10 that presumably is
also fixed in 3.0.13.  I just installed 3.0.13 on a system with
~80000 users and ~80000 groups where wbinfo -u
does not return a userlist but wbinfo -g lists the groups.
See bug #2567. <https://bugzilla.samba.org/show_bug.cgi?id=2567>
Are you running Linux? what kernel version?  With 2.4
it's still neccessary to modify NGROUPS_MAX in limits.h
otherwise a user can only be member of max 32 groups.

    Peter

Peter Kruse <pk@q-leap.com> writes:
> The winbind startup with that many users takes loong, but
> that is fixed in 3.0.13.  We observed the same memory
> leak in winbind in version 3.0.10 that presumably is
> also fixed in 3.0.13.  I just installed 3.0.13 on a system with
> ~80000 users and ~80000 groups where wbinfo -u
> does not return a userlist but wbinfo -g lists the groups.
I have testet wbinfo -g again on the ~90000 groups, and winbindd tries
to use all the memory and I have to kill it. How much memory does your
winbindd end up using when you do wbinfo -g ?

-- 
Kim Hansen