Re: ypbind problem

[miquels@cistron.nl (Miquel van Smoorenburg)]

In article <39E7CC5A.B7F0BA25@aphroland.org>,
Nate Amsden  <aphro@aphroland.org> wrote:
>Douglas Eck wrote:
>> 
>> Anyone know if it's normal for ypbind to spawn four daemons that
>> eat up 16Mb of memory? It works fine... but seems like a lot
>> of overhead. I'm running woody...
>> 
>> >From memstat:
>>    4180k: PID  6497 (/usr/sbin/ypbind)
>>    4180k: PID  6496 (/usr/sbin/ypbind)
>>    4180k: PID  6495 (/usr/sbin/ypbind)
>>    4180k: PID  6492 (/usr/sbin/ypbind)
>
>since they are all reporting the exact same memory usage i'd say it is
>just forks of the same program, all of th em are using 4180k combined. 

Threads, to be precise. "ps" doesn't know how to distinguish between
one program with several threads and distinct processes. This is
because the kernel doesn't export that information. It might get fixed
in the 2.4 kernels (and a new procps that is aware of that ofcourse)

But 4180k is pretty big. On one of my systems:

% psgrep ypbind
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root     19638  0.0  0.2  1308  744 ?        S    Oct09   0:00 /usr/sbin/ypbind
root     19640  0.0  0.2  1308  744 ?        S    Oct09   0:00 /usr/sbin/ypbind
root     19641  0.0  0.2  1308  744 ?        S    Oct09   0:00 /usr/sbin/ypbind
root     19642  0.0  0.2  1308  744 ?        S    Oct09   0:00 /usr/sbin/ypbind

Mike.