Ed Garcia wrote:
Hello,
I am encountering a strange behaviour of ypbind. I wonder if anyone here has an idea of what could be the problem ...
Note: This is after a fresh installation of SuSE 9.1 and a straightforward NIS Client setup via YaST.
On boot up, ypbind attempts to start but it takes too long (10+ minutes) only to end up with a "NO NIS SERVER FOUND" message and a *failed* status. Strange thing is, after bootup is finished, it seems that ypbind is running properly! rcypbind status returns a *running* status and KDE shows all users coming in from the NIS server and the users are able to logon and do their work as if they were working on the server.
In short ... ypbind says it fails on boot but it seems to work perfectly after boot!?!.
With NIS working properly I should actually be happy, but the extra long bootup time and the "NO NIS SERVER FOUND" failed message bothers me. Is this a bug? or a wrong setting somewhere? I am using SuSE 9.1. The behaviour is same with using either Professional and Personal versions on the client. I use Professional as the NIS server.
Thanks so much, been bugged by this strange behaviour for 3 weeks now. I ran out of clues on why this could be happening.
Hi, I've got messages like yours in random services (mostly sshd, mysql and apache) and everything was file, everything running, nothing in logs. (Suse 9.0) This problem was solved when I changed in /etc/sysconfig/boot RUN_PARALLEL from 'yes' to 'no'. Boottime was longer, but as I don't plan to reboot too often, I prefer to wait a little bit more and see correct messages. -- Marcos Lazarini