ypserv answers very slow/too late for login manager

Hello,

I'm a teacher in germany, so please ignore my "funny" english.
The german text follows below.


I have a SuSE 9.3 network in school with a server for NIS and /home
and yone room with 14 clients and one with 8. After clients update to 10.1
(actualized with smart) I'm having a big problem with ypserv/ypbind. On
every second machine the login manager shows none of the 600 user names when
the PCs are started for first time. A restart of X solves it.

On console nr 1 the boot screen shows "ypbind ....." instead of "ypbind ."
on the correct ones. I think, that this is the problem.

Is it possible to tell ypserv to creat a logfile?
Is it possible to tune up ypserv.
Would an update of the server to 10.1 be a solution?
Should I use 10.0?

I've no idea (yet) where to screw :-(.


There are only 14 clients, so the server should be fast enough (1,3 GHz,
2 GB RAM, 100MBit network, one unmanaged switch).

Any idea would be great !
<english />

<Deutsch>
ich habe meine Schüler-PCs auf 10.1 upgedatet, um nach den Sommerferien
mit dem aktuellen System zu arbeiten. Ich habe dazu einen "Master"
eingerichtet und anschließend die Festplatten mit UDP-Cast geklont und
die Netzwerkkarte neu eingestellt. Jeder Rechner einzeln funktionert
wunderbar.

Wenn ich mehrere Rechner (13) gleichzeitig einschalte, zeigt nur jeder
zweite Rechner die vorhandenen User im Anmeldemanager. Ein X-Neustart
fordert sie dennoch zutage.

Die Boot-Konsole zeigt zwei Unterschiede:
Â*1. Reihenfolge der Dienste unterschiedlich
Â*2. ypbind mit einem oder mehreren Punkten (. oder ........)

Meine Vermutung ist, dass der ypserver manchmal zulange braucht
und X dann schon gestartet ist, so dass der Anmeldemanager keine
User anzeigen kann.

Ich habe im NIS HowTo und in meinem schlauen Buch nichts gefunden.


Wie kann ich yp zu einem log-file ermutigen, bzw. yp beschleunigen?

Ist es wichtig, dass der Server auch mit 10.1 statt 9.3 läuft?


Ich bin für jeden sachdienlichen Hinweis dankkbar!
<Deutsch />


Ciao Michael

Michael van Gemmern wrote:
> Hello,
>
> I'm a teacher in germany, so please ignore my "funny" english.
> The german text follows below.

Ihr englisch ist besser als mein deutsch.
>
>
> I have a SuSE 9.3 network in school with a server for NIS and /home
> and yone room with 14 clients and one with 8. After clients update to 10.1
> (actualized with smart) I'm having a big problem with ypserv/ypbind. On
> every second machine the login manager shows none of the 600 user names when
> the PCs are started for first time. A restart of X solves it.
>
> On console nr 1 the boot screen shows "ypbind ....." instead of "ypbind ."
> on the correct ones. I think, that this is the problem.
>
> Is it possible to tell ypserv to creat a logfile?
> Is it possible to tune up ypserv.
> Would an update of the server to 10.1 be a solution?
> Should I use 10.0?
>
> I've no idea (yet) where to screw :-(.
>
>
> There are only 14 clients, so the server should be fast enough (1,3 GHz,
> 2 GB RAM, 100MBit network, one unmanaged switch).
>
> Any idea would be great !

On a server that does not anyone using the keyboard, there is frequently too little entropy for
/dev/random to provide a random number for the password hashing. Under these conditions, /dev/random
will block. On the other hand, /dev/urandom never blocks. If the entropy pool is low, it returns as
good a random number as it can. The security is not as good, but it is probably good enough for your
purposes. If this is the source of your delay, perform the following steps as root:

mv /dev/random /dev/random.save
ln -s /dev/urandom /dev/random

Later kernel versions seem not to block, but I cannot prove that.

Guten Tag,

Larry

Hi Larry,



Larry Finger wrote:
> Michael van Gemmern wrote:
>> I have a SuSE 9.3 network in school with a server for NIS and /home
>> and yone room with 14 clients and one with 8. After clients update to
>> 10.1 (actualized with smart) I'm having a big problem with ypserv/ypbind.
>> On every second machine the login manager shows none of the 600 user
>> names when the PCs are started for first time. A restart of X solves it.
>>
>> On console nr 1 the boot screen shows "ypbind ....." instead of "ypbind
>> ." on the correct ones. I think, that this is the problem.
>>
>> Is it possible to tell ypserv to creat a logfile?
>> Is it possible to tune up ypserv.
>> Would an update of the server to 10.1 be a solution?
>> Should I use 10.0?
>>
>> I've no idea (yet) where to screw :-(.
>>
>>
>> There are only 14 clients, so the server should be fast enough (1,3 GHz,
>> 2 GB RAM, 100MBit network, one unmanaged switch).
>>
>> Any idea would be great !
>
> On a server that does not anyone using the keyboard, there is frequently
> too little entropy for /dev/random to provide a random number for the
> password hashing. Under these conditions, /dev/random will block. On the
> other hand, /dev/urandom never blocks. If the entropy pool is low, it
> returns as good a random number as it can. The security is not as good,
> but it is probably good enough for your purposes. If this is the source of
> your delay, perform the following steps as root:
>
> mv /dev/random /dev/random.save
> ln -s /dev/urandom /dev/random
>
> Later kernel versions seem not to block, but I cannot prove that.

thanks for your answer, but that doesn't made any difference. Perhaps
its not ypserv but the nfs-share. I wish, I had more time and more
knowledge of ethereal output :-(.


Ciao Michael