2009/1/17 Jesse Keating <jkeating@xxxxxxxxxxxxxxx>
AFAICT, it is not possible if the error was something like "On Sat, 2009-01-17 at 12:23 -0800, Jesse Keating wrote:Never mind. Turns out that the client couldn't be looked up via it's IP
> 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?
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.
Nov 7 19:14:40 fc10 rpc.mountd: Fake hostname bogus.com for 192.168.1.1 - forward lookup doesn't exis"
This is a security precaution added into the nfs package that lessens the likelihood of unauthorized servers from gaining access to files on the NFS server. Look to
nfs-utils-1.1.4/support/export/hostname.c
Regards
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
