Re: nfscbd does not update mtime

On Sun, Feb 23, 2025 at 3:09 PM Peter 'PMc' Much
<pmc@citylink.dinoex.sub.org> wrote:
>
>
> Hello,
>
>  after some discussion earlier concerning a runaway nfscbd process
> (which luckily did not repeat), I decided to correctly (hopefully)
> engage the feature.
>
> But now I find it has a side-effect: one cannot compile ports, because
> the mtime isn't right. The result is then like that:
>
>
> /usr/ports/security/openvpn/work/openvpn-2.6.13/missing: aclocal-1.16: not found
> WARNING: 'aclocal-1.16' is missing on your system.
> *** [./aclocal.m4] Error code 127
> make[3]: stopped in /usr/ports/security/openvpn/work/openvpn-2.6.13
>
>
> The cause is the the mtime are not updated to those that were in the
> tarball, but stay at the time of unpacking the tarball. And that
> doesn't work well with make.
>
> Then I kill the nfscbd processes, and my timestamps are correct. I
> start the nfscbd again, umount and mount, unpack an archive, and
> it keeps the wrong (current) timestamps.
> So this is certainly the cause - but what is going wrong? Or what am
> I doing wrong?
>
> I'm still at 13.4, and the share comes from ZFS and is created for
> the exclusive use on a single client.
First off, are you using a FreeBSD client or a Linux one, or ???
Also, what mount options are in use.
# nfsstat -m
on the client, lists what is actually being used. (Works for both Linux and
FreeBSD.)

Have you set vfs.nfsd.issue_delegations non-zero on the server?
(If not, there is really no use for the nfscbd, since it should only get
callbacks when delegations are issued.)

rick
>
>
> cheerio,
> PMc