From: Tommi Virtanen <tommi.virtanen@dreamhost.com>
To: Colin Patrick McCabe <colin.mccabe@dreamhost.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: g_conf.id, g_conf.name, g_conf.type and friends
Date: Wed, 23 Feb 2011 14:28:41 -0800 [thread overview]
Message-ID: <20110223222841.GB30697@dreamer> (raw)
In-Reply-To: <20110223221353.GA30697@dreamer>
On Wed, Feb 23, 2011 at 02:13:53PM -0800, Tommi Virtanen wrote:
> > *** g_conf.type: nobody seems to know what this is.
> > It seems like at one point, g_conf.type was intended to be one of
> > "auth", "mon", "osd", "mds", or "client".
>
> This seems to be tied to cconf's use of "type" as in sections "osd0"
> and "osd.0" are both type=osd, id=0. So, it soudns to be like it's
> there mostly to get around the fact that config section names are not
> predictable.
On a related note, this was fairly frustrating to debug:
$ cauthtool --create-keyring --gen-key --name=foo.42 test
creating test
$ cat test
[client.42]
key = AQCBiWVNuCl4ABAAJjvKiiQvtksfOJtJV8sR9A==
auid = 18446744073709551615
I hate it when programs silently ignore what I explicitly tell them to
do. cauthtool ignores --name= if it doesn't fit it's expectations.
Why aren't the key names just unique strings?
--
:(){ :|:&};:
next prev parent reply other threads:[~2011-02-23 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 21:58 g_conf.id, g_conf.name, g_conf.type and friends Colin Patrick McCabe
2011-02-23 22:13 ` Tommi Virtanen
2011-02-23 22:26 ` Colin Patrick McCabe
2011-02-23 22:42 ` Sage Weil
2011-02-23 22:28 ` Tommi Virtanen [this message]
2011-02-23 22:46 ` Yehuda Sadeh Weinraub
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=20110223222841.GB30697@dreamer \
--to=tommi.virtanen@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=colin.mccabe@dreamhost.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 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.