From: Helge Kreutzmann <debian@helgefjell.de>
To: alx.manpages@gmail.com
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Issue in man page nfsservctl.2
Date: Wed, 1 Nov 2023 14:02:11 +0000 [thread overview]
Message-ID: <ZUJaY4vT3lwVt9mq@meinfjell.helgefjelltest.de> (raw)
Without further ado, the following was found:
Issue: mountd(8) → B<mountd>(8)
"/*\n"
" * These are the commands understood by nfsctl().\n"
" */\n"
"#define NFSCTL_SVC 0 /* This is a server process. */\n"
"#define NFSCTL_ADDCLIENT 1 /* Add an NFS client. */\n"
"#define NFSCTL_DELCLIENT 2 /* Remove an NFS client. */\n"
"#define NFSCTL_EXPORT 3 /* Export a filesystem. */\n"
"#define NFSCTL_UNEXPORT 4 /* Unexport a filesystem. */\n"
"#define NFSCTL_UGIDUPDATE 5 /* Update a client\\[aq]s UID/GID map\n"
" (only in Linux 2.4.x and earlier). */\n"
"#define NFSCTL_GETFH 6 /* Get a file handle (used by mountd(8))\n"
" (only in Linux 2.4.x and earlier). */\n"
"\\&\n"
"struct nfsctl_arg {\n"
" int ca_version; /* safeguard */\n"
" union {\n"
" struct nfsctl_svc u_svc;\n"
" struct nfsctl_client u_client;\n"
" struct nfsctl_export u_export;\n"
" struct nfsctl_uidmap u_umap;\n"
" struct nfsctl_fhparm u_getfh;\n"
" unsigned int u_debug;\n"
" } u;\n"
"}\n"
"\\&\n"
"union nfsctl_res {\n"
" struct knfs_fh cr_getfh;\n"
" unsigned int cr_debug;\n"
"};\n"
next reply other threads:[~2023-11-01 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 14:02 Helge Kreutzmann [this message]
2023-11-01 15:44 ` Issue in man page nfsservctl.2 Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2023-03-11 17:13 Helge Kreutzmann
2023-03-11 23:31 ` Alejandro Colomar
2023-03-12 5:23 ` Helge Kreutzmann
2023-03-12 17:11 ` G. Branden Robinson
2023-03-12 17:55 ` Helge Kreutzmann
2023-01-22 19:31 Helge Kreutzmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZUJaY4vT3lwVt9mq@meinfjell.helgefjelltest.de \
--to=debian@helgefjell.de \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).