Jesse Keating wrote: > On Sat, 2009-01-17 at 12:23 -0800, Jesse Keating wrote: >> I've got an F10 box acting as the NFS server, and I'm getting failures >> loading the install.img from NFS. The failures are of the type that it >> cannot mount the directory, even though I can from another host, so I >> have to think that something weird is going on server side. Does >> anybody know of a way to increase the verbosity of the nfs server >> daemons so that I can see what it is getting from the client? > > Never mind. Turns out that the client couldn't be looked up via it's IP > address, so mount said no (even though it was a warning in the log, not > an error). Anybody know how to instruct nfs to not care about this? I > didn't see anything in a quick scan of the exports man page. The discussion about the fact mountd (statd) no longer accept connections from unknown IP address (similar to other system daemon) due to a "fix" in the tcp wrapper code is at: https://bugzilla.redhat.com/show_bug.cgi?id=448898 and https://bugzilla.redhat.com/show_bug.cgi?id=480420 Through some side bar discussion it been suggested an update to the man page is probably need (which I agree) and maybe a flag of some sort to allow unknown IP address access. I must admit, I'm a bit hesitant to do the later, since I don't think its a good idea to allow unknown client access any system daemon... steved. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
