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?
--
:(){ :|:&};:
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
