On Wed, Apr 22, 2009 at 10:58:37AM +0200, Edward Welbourne wrote: > > Since ypbind is able to discover servers automatically
> What needs to be set up to make that work ? > Getting that configured (presumably on the local network) would indeed > make this a non-problem, at least for me. Describing these details in It should Just Work with no setup required if the server is on the same subnet - I'll need to test again but this did work last time I tried. > the package's README.Debian might help, too ... I'm unable to get a > clue from man ypbind, and /usr/share/doc/nis/nis.debian.howto.gz only > tells me how to set up each host, not what network (DHCP?) config will > ensure that ypbind can discover the right server without me having to > hand-edit yp.conf and restart nis after it's failed to start on > install; or is this just some detail of the NIS server config, > e.g. making it listen for broadcast ? The server not listening for broadcast is the most likely explanation. The thing that's supposed to deal with the broadcasts is actually portmap rather than ypserv itself. Looking at the manual page I can't immediately see an option that would stop this without also breaking the rest of nis. I'll have a look when I'm not at work. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
