Page MenuHomeFreeBSD

update the man page for having nolockd enabled for NFSv4
ClosedPublic

Authored by rmacklem on Sep 5 2022, 9:01 PM.
Tags
None
Referenced Files
F102354941: D36462.id110329.diff
Mon, Nov 11, 3:28 AM
Unknown Object (File)
Oct 3 2024, 3:38 AM
Unknown Object (File)
Oct 3 2024, 3:38 AM
Unknown Object (File)
Oct 3 2024, 3:38 AM
Unknown Object (File)
Oct 3 2024, 3:37 AM
Unknown Object (File)
Oct 3 2024, 3:25 AM
Unknown Object (File)
Sep 24 2024, 3:39 AM
Unknown Object (File)
Sep 23 2024, 8:21 AM
Subscribers

Details

Summary

Commit 33721eb991d8 enabled the use of the "nolockd"
option for NFSv4 mounts. The main reason for doing this
is to allow it to be used along with the "intr" mount option,
so that file locks are not left in a indeterminate state on the
NFS server when an RPC is interrupted by a signal.

This patch updates the man page.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

sbin/mount_nfs/mount_nfs.8
338–340

This sentence was ambiguous before (does "not" apply to "handle locks"?), and this makes it more convoluted. I'd suggest breaking it up, e.g. "do not use these daemons. They handle locks ... unless this option is specified.

Split sentence into two sentences, as suggested by karels@.

I don't know if manpages have any comments, but this looks good to me.

This revision is now accepted and ready to land.Sep 7 2022, 3:15 AM
gbe added a subscriber: gbe.

LGTM.