Lads, I just spent an hour tracking down why a nis client could not find the nis server, which it was itself.
ypbind -debug revealed something weird about NetworkManager. Now that is probably a great program for laptops and such, but it doesn't interact with a static network setup, which I use for my servers---I realize I am a bit old-fashioned. So the dbus-networkmanager-whatever magic claimed there were no working network interfaces---which is not true, they are there but static. So the existence of networkmanager caused ypbind to simply not do anything and wait. Without any diagnostics, as fasr as I can tell. As nis is old---maybe default to old-fashioned static network behaviour. I sure can't wait for a proper replacement of nis. Sorry, ---david -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
