From: Juan Gomez <juang@us.ibm.com>
To: Shaya Potter <spotter@cs.columbia.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfsservctl documentation?
Date: Mon, 30 Dec 2002 10:34:35 -0800 [thread overview]
Message-ID: <OF0BDEC488.45CFEF00-ON87256C9F.0065D913@us.ibm.com> (raw)
Well you have the best documentation of all: the code itself. I did not
find anything else other than the man page when trying to undestand it but
the code was easy to follow.
Juan
|---------+---------------------------------->
| | Shaya Potter |
| | <spotter@cs.columbia.ed|
| | u> |
| | Sent by: |
| | linux-kernel-owner@vger|
| | .kernel.org |
| | |
| | |
| | 12/29/02 09:30 PM |
| | |
|---------+---------------------------------->
>-------------------------------------------------------------------------------------------------------------------------|
| |
| To: linux-kernel@vger.kernel.org |
| cc: |
| Subject: nfsservctl documentation? |
| |
>-------------------------------------------------------------------------------------------------------------------------|
is there any real documentation on this syscall anywhere? i.e. if one
wanted to write a daemon that dynamically dealt with nfs exports
(creating/removing/changing) this syscall would seem very appropriate
(at least as I understand), but I can't find any documentation besides
the skimpy man page on how to use it.
am I not supposed to use it? :)
thanks,
shaya
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2002-12-30 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 18:34 Juan Gomez [this message]
2002-12-30 20:12 ` Andries Brouwer
-- strict thread matches above, loose matches on Subject: below --
2002-12-30 5:30 Shaya Potter
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=OF0BDEC488.45CFEF00-ON87256C9F.0065D913@us.ibm.com \
--to=juang@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spotter@cs.columbia.edu \
/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
all inboxes | Powered by JetHome®