en Copyright 2015 Java http://172.16.0.5:8080/history/freebsd-13.1/libexec/rc/rc.d/mountd#85ad4936 mountd(8): generate a syslog message when the "V4:" line is missingDaniel reported that NFSv4 mounts were not working despite havingset "nfsv4_server_enable=YES" in /etc/rc.conf. Mountd was logging amessage that there was no /etc/exports file.He noted that creating a /etc/exports file with a "V4:" line in itwas needed make NFSv4 mounts work.At least one "V4:" line in one of the exports(5) file(s) is needed tomake NFSv4 mounts work. This patch fixes mountd.c so that it logs amessage indicting that there is no "V4:" line in any exports(5)file when NFSv4 mounts are enabled.To avoid this message being generated erroneously, /etc/rc.d/mountdis updated to make sure vfs.nfsd.server_max_nfsvers is properly setbefore mountd(8) is started.PR: 253901(cherry picked from commit 09673fc0f36dd1cca74940a240a9ed0f62228084) List of files: /freebsd-13.1/libexec/rc/rc.d/mountd Tue, 09 Mar 2021 00:08:02 +0000 Rick Macklem <rmacklem@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-13.1/libexec/rc/rc.d/mountd#4389a566 Add support for the new mountd -R option.r376026 added a new "-R" option to mountd, which tells it tonot support the Mount protocol (not used by NFSv4) and notregister with rpcbind.Rpcbind is considered a security issue by some sites now.This patch adds a new yes/no variable called nfsv4_server_only.When that is set, make vfs.nfsd.server_min_vers=4 and set "=R"for mountd.Setting vfs.nfsd.server_min_vers=4 tells nfsd to not register with rpcbind.While here, add a check for "load_kld nfsd" failing to nfsd.Reviewed by: 0mpMFC after: 2 weeksDifferential Revision: https://reviews.freebsd.org/D26938 List of files: /freebsd-13.1/libexec/rc/rc.d/mountd Fri, 06 Nov 2020 16:33:42 +0000 Rick Macklem <rmacklem@FreeBSD.org> http://172.16.0.5:8080/history/freebsd-13.1/libexec/rc/rc.d/mountd#0696600c Move the rc framework out of sbin/init into libexec/rc.The reasons for this are forward looking to pkgbase: * /sbin/init is a special binary; try not to replace it with every package update because an rc script was touched. (a follow-up commit will make init its own package) * having rc in its own place will allow more easy replacement of the rc framework with alternatives, such as openrc.Discussed with: brd (during BSDCam), kmooreRequested by: cem, bzPR: 231522Approved by: re (gjb) List of files: /freebsd-13.1/libexec/rc/rc.d/mountd Wed, 17 Oct 2018 16:49:11 +0000 Bjoern A. Zeeb <bz@FreeBSD.org>