<div class="gmail_quote">2009/1/17 Jesse Keating <span dir="ltr"><<a href="mailto:jkeating@j2solutions.net">jkeating@j2solutions.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Sat, 2009-01-17 at 12:23 -0800, Jesse Keating wrote:<br>
> I've got an F10 box acting as the NFS server, and I'm getting failures<br>
> loading the install.img from NFS. The failures are of the type that it<br>
> cannot mount the directory, even though I can from another host, so I<br>
> have to think that something weird is going on server side. Does<br>
> anybody know of a way to increase the verbosity of the nfs server<br>
> daemons so that I can see what it is getting from the client?<br>
<br>
</div>Never mind. Turns out that the client couldn't be looked up via it's IP<br>
address, so mount said no (even though it was a warning in the log, not<br>
an error). Anybody know how to instruct nfs to not care about this? I<br>
didn't see anything in a quick scan of the exports man page.<br>
<font color="#888888"></font></blockquote><div><br><br></div></div>AFAICT, it is not possible if the error was something like "<br><pre>Nov 7 19:14:40 fc10 rpc.mountd: Fake hostname <a href="http://bogus.com">bogus.com</a> for 192.168.1.1 - forward lookup doesn't exis</pre>
"<br>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 <br>nfs-utils-1.1.4/support/export/hostname.c<br><br>Regards<br><br>