Winbind slowing down entire system

[Michels, Gustavo [EES/BR]]

Hi,

I am currently testing with winbind enum users and groups set as no to see
memory consumption.

Winbind is really eating up everything here, even without many usage. The
test server is only acting as a time server for our resource domain users
(about 100 users) and is serving as a test print server for 3 clients, using
cups.

I restarted the server last night and this morning winbind was taking 70% of
the system memory (512 RAM and 512 swap total)

I still can't understand why it just started eating up the whole system...

cheers
Gustavo

> -----Original Message-----
> From: Anthony J. Breeds-Taurima [mailto:tony at cantech.net.au]
> Sent: terça-feira, 25 de setembro de 2001 23:50
> To: Michels, Gustavo [EES/BR]
> Cc: cary_dickens2 at hp.com; samba at lists.samba.org
> Subject: RE: Winbind slowing down entire system
> 
> 
> On Mon, 24 Sep 2001, Michels, Gustavo [EES/BR] wrote:
> 
> > Taking winbind out of the group line in nsswitch.conf 
> really wiped away the
> > pause while I was telnetting in. But the problem is I need 
> domain groups
> > because my share's security are set by domain group membership.
> >
> > So, I must find other solution... :-( This is really 
> strange as last friday
> > my server wasn't like this, only with this new cvs sources 
> this slowdown
> > started. Actually, the telnet delay was present (although 
> there wasn't a
> > delay, let's say, with 2 weeks ago sources), but winbind 
> wasn't eating up
> > the whole system resources.
> 
> Hmm isn't this what "winbind enum users" is for.
> 
>        winbind enum users
>               On  large installations it may be necessary to sup-
>               press the enumeration of users through  the   setp-
>               went(),  getpwent()  and endpwent() group of system
>               calls. If  the  winbind  enum  users  parameter  is
>               false,  calls  to the getpwent system call will not
>               return any data.
> 
>               Warning: Turning off  user  enumeration  may  cause
>               some  programs  to  behave  oddly. For example, the
>               finger program relies on having access to the  full
>               user list when searching for matching usernames.
> 
>               Default: winbind enum users = yes
> 
> See if that helps.
> 
> Yours Tony.
> 
> /*
>  * "The significant problems we face cannot be solved at the
>  * same level of thinking we were at when we created them."
>  * --Albert Einstein
>  */
>