Page MenuHomeFreeBSD

update exports.5 to include information on the TLS export options
ClosedPublic

Authored by rmacklem on Aug 31 2020, 2:02 AM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 28 2023, 12:59 AM
Unknown Object (File)
Dec 20 2023, 6:12 AM
Unknown Object (File)
Nov 28 2023, 5:44 AM
Unknown Object (File)
Nov 27 2023, 11:03 AM
Unknown Object (File)
Nov 25 2023, 11:54 AM
Unknown Object (File)
Nov 24 2023, 8:28 PM
Unknown Object (File)
Nov 24 2023, 7:36 PM
Unknown Object (File)
Nov 23 2023, 2:13 AM
Subscribers

Details

Reviewers
gbe
Group Reviewers
manpages
Summary

NFS over TLS uses three new export options, added by r364979.
This patch updates the exports.5 man page for these new options.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 33636

Event Timeline

bjk added inline comments.
exports.5
256

Two esses in rpctlssd??
Also, purists might say that since rpctlsd is a daemon, we should just say "[...] to work, rpctlsd must be running [...]"

Take "the" and "daemon" out as suggested by bjk@.

Replied to inline comment and asked if rpc.tlssd would be preferable
to rpctlssd?

exports.5
256

There are two daemons, one for the client and the
other for the server called rpctlscd and rpctlssd.
You might be able to guess which is which;-)

I did not use the Sun trandition of putting a "."
in the name (rpc.tlscd, rpc.tlssd).
If you or others would prefer the "." in the name,
I can easily change that.

rpokala added inline comments.
exports.5
256

I did not use the Sun trandition of putting a "."
in the name (rpc.tlscd, rpc.tlssd).
If you or others would prefer the "." in the name,
I can easily change that.

FWIW, I think the separator makes things easier to read. Thanks!

Rename rpctlssd to rpc.tlsservd, since that seemed to
be the preferred name for the daemon and this
hopefully will avoid confusion with the one for
the client side.

gbe added inline comments.
exports.5
254

The RFC should me updated to the real RFC and it would nice if the RFC could be mentioned in the SEE ALSO or STANDARDS section.

Added some replies to inline comments.

exports.5
254

Agreed, except it does not have a number yet.
It has been in "last call" (or whatever IETF calls
it) for many weeks now.
I am planning on fixing it as soon as the RFC
gets published. (I didn't see any point in
referencing the Internet Draft, since this should
happen before FreeBSD-13 gets released.

I will also add a reference in SEE ALSO when
it gets published. (I suppose I could do that
now, since I know the title, just not the NNNN.)

Added some replies to inline comments.

Hi Rick,

I wasn't aware that the RFC is still pending, so first, let me thank you, that you will include the RFC details in the man page,
and second for working on features, that will be become handy in the future. :)

  • Gordon

Added a STANDARDS section, as suggested by gbe@.

This revision is now accepted and ready to land.Nov 19 2020, 4:36 PM

Committed. I typed review.freebsd.org instead of reviews.freebsd.org
in the commit message and, as such, it didn't autoclose.