From: Florian Haas <florian@hastexo.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: radosgw-admin: mildly confusing man page and usage message
Date: Mon, 11 Jun 2012 23:35:54 +0200 [thread overview]
Message-ID: <4FD664BA.6040801@hastexo.com> (raw)
Hi,
just noticed that radosgw-admin comes with a bit of confusing content in
its man page and usage message:
EXAMPLES
Generate a new user:
$ radosgw-admin user gen --display-name="johnny rotten"
--email=johnny@rotten.com
As far as I remember "user gen" is gone, and it's now "user create".
However:
radosgw-admin user create --display-name="test" --email=test@demo
user_id was not specified, aborting
... is followed by a usage message that doesn't mention user_id anywhere
(the option string is --uid). So conceivably the example could also use
a mention of --uid.
Also, is there a way to retrieve the "next available" user_id or just
tell radosgw-admin to use max(user_id)+1?
If one of the Ceph guys could provide a quick comment on this, I can
send a patch to the man page RST. Thanks.
Cheers,
Florian
next reply other threads:[~2012-06-11 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 21:35 Florian Haas [this message]
2012-06-11 21:39 ` radosgw-admin: mildly confusing man page and usage message Yehuda Sadeh
2012-06-11 21:57 ` Florian Haas
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=4FD664BA.6040801@hastexo.com \
--to=florian@hastexo.com \
--cc=ceph-devel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.