That's just the script the starts the software. The actual software is
fetched and build and installed in this recipe:
https://git.yoctoproject.org/poky/tree/meta/recipes-connectivity/nfs-utils/nfs-utils_2.4.1.bb?id=8a1e7bd5dc9bbf7531fcc66427847448c71ec64c
If you look into the nfs-utils source tr
I am using the 'nfsserver' script from yocto's poky repository, so this issue
should also be related to yocto?
https://git.yoctoproject.org/poky/tree/meta/recipes-connectivity/nfs-utils/nfs-utils/nfsserver?id=8a1e7bd5dc9bbf7531fcc66427847448c71ec64c
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all
I guess this should be raised with nfsd upstream? Their answer is
authoritative, we'd be only guessing.
Alex
On Thu, 29 Aug 2024 at 15:35, pangliyuan1 via lists.yoctoproject.org
wrote:
>
> Hello,
>
> Recently, when I execute 'nfsserver stop' to stop nfsd service, I find that
> nfsd threads cann
Hello,
Recently, when I execute 'nfsserver stop' to stop nfsd service, I find that
nfsd threads cannot be killed.
>
> # nfsserver stop
> stopping statd: done
> stopping mountd: done
> stopping nfsd: ..failed
> using signal 9:
> ..failed
>
I noticed that nfsserver script uses '