In article [EMAIL PROTECTED],
Nate Amsden [EMAIL PROTECTED] 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
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)
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
I have a small problem with ypbind. Master NIS server is running at
192.168.1.100 (network 192.168.96/255.255.255.224) and client machine
is at 192.168.1.37 (network 192.168.1.32/255.255.255.224).
When I start ypbind it tries to find out master server by broadcasts, even
if I specify domain and
On Mon, 23 Jun 1997, Sami Laine wrote:
I have a small problem with ypbind. Master NIS server is running at
192.168.1.100 (network 192.168.96/255.255.255.224) and client machine
is at 192.168.1.37 (network 192.168.1.32/255.255.255.224).
When I start ypbind it tries to find out master server
5 matches
Mail list logo