yes, no problem, we have a box where this should be no problem.
Can you point me to a short howto, how I can do this?
----- Originalnachricht -----
Von: Volker Lendecke <Volker.Lendecke@xxxxxxxxx>
Gesendet: Don, 1.10.2009 10:08
An: Dr. Hansjoerg Maurer <hansjoerg.maurer@xxxxxxx>
Betreff: Re: winbind 3.3.7 memory usage
On Thu, Oct 01, 2009 at 09:45:16AM +0200, Dr. Hansjoerg Maurer wrote:
> attached you see the pool-usage of the "big" winbindd
> But I did not see any big numbers in the output
Ok, then the memleak is somewhere else, in non-talloc
controlled malloc memory. The only real way to find it is to
run the process under valgrind. This makes it very, very
slow though. Do you have a test box that you can put similar
load on where you could live with a slow winbind?