On Sun, Aug 12, 2007 at 11:33:38PM -0500, Nelson Castillo wrote: > I don't think it is clear at all. I'm talking about the default configuration > of nfs-kernel-server, that should at least work from localhost with no > extra configuration, IMHO. > > If there is some reason that precludes nfs-kernel-server to work out of > the box, perhaps there should be a README in /usr/share/doc/nfs-kernel-server. > I looked for a hint there. If you tell me what I have to write, I'll > happily do it.
Let me see if I understand this right: - Recent portmap binds to 127.0.0.1 only by default. (At least Anibal claims so; I cannot reproduce that, though, and default for the debconf question "portmap/loopback" is false.) - nfs-kernel-server cannot work if portmap is bound to 127.0.0.1 -- this is reasonable (NFS is, after all, a network service), but the error should be better documented. Is my understanding of the situation right? In that case, I'd be happy to update README.Debian with a note documenting this behavior, although it looks to me as if the debconf question is already quite explicit about the issue (my capitalization): Portmap by default listens to all IP addresses. However, if you are not providing network RPC services to remote clients (YOU ARE IF YOU ARE SETTING UP A NFS OR NIS SERVER) you can safely bind it to the loopback IP address (127.0.0.1) [...] /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
