On Wed, Dec 02, 2009 at 08:43:35AM -1000, Ryo Furue wrote: > Because our NIS servers are not on the same subnet as > my machine. I think it's one of the purposes of yp.conf > to specify NIS servers when they are on different subnets > (that is, when they are not reachable by broadcast). > Is that right?
Yes, that's the situation where configuration of /etc/yp.conf is essential. > I don't know at all how common or rare the situation is > where NIS servers are on different subnets. Regardless, It's pretty rare. Most systems have a NIS slave on each network segment for performance reasons so the problem doesn't arise. > I don't think any debconf process should fail > when the user didn't give wrong parameters to it. > (And I consider this particular case as a failure > because ypbind gets stuck for 30 seconds or a minute > and says "failed" in red letters.) > In the case of the nis package, the user isn't given > a chance of giving correct parameters to the debconf > process. It's not actually failed - this is just a problem with the way the standardised output stuff works, it'd probably be better to just change the output to a success one. With the model Debconf has there's really not much constructive we can do here - the sort of configuration you need to do to set up a NIS master server is really not at all appropriate for configuration within Debconf where the UI elements are disconnected from the programmatic control and probably need to be done as a post installation activity. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
