Ok, I had a hunch it was related to the use of jails.
I am just testing a patch that switches the nfsuserd over to
using an af_local socket, so this will be avoided.
(I think it makes more sense anyhow. I just never got around
to doing it.;-)
Thanks for the info, rick
- Original Message
On Thu, 10 Dec 2015, Rick Macklem wrote:
> Hi,
>
> Mark has reported a problem via email where the nfsuserd daemon sees
> requests coming from an IP# assigned to the machine instead of 127.0.0.1.
> Here's a snippet from his message:
> Ok, I have Plex in a jail and when I scan the remote NFS file
On Thu, Dec 10, 2015, at 07:37, Rick Macklem wrote:
> Hi,
>
> Mark has reported a problem via email where the nfsuserd daemon sees
> requests coming from an IP# assigned to the machine instead of 127.0.0.1.
> Here's a snippet from his message:
> Ok, I have Plex in a jail and when I scan the re
I think a local socket is probably the best solution long term. Using a
local socket also allows using filesystem permissions to control access
which is required for gssd but not necessarily for nfsuserd.
On 10 December 2015 at 13:37, Rick Macklem wrote:
> Hi,
>
> Mark has reported a problem vi
Hi,
Mark has reported a problem via email where the nfsuserd daemon sees
requests coming from an IP# assigned to the machine instead of 127.0.0.1.
Here's a snippet from his message:
Ok, I have Plex in a jail and when I scan the remote NFS file share the
*local* server's nfsuserd spams the logs
