From: Ken Dreyer <kdreyer@redhat.com>
To: Tim Serong <tserong@suse.com>, Sage Weil <sweil@redhat.com>
Cc: Gaudenz Steinlin <gaudenz@debian.org>,
ceph-devel@vger.kernel.org, cjwatson@debian.org,
ceph-maintainers@ceph.com, timm@fnal.gov,
Owen Synge <osynge@suse.com>
Subject: Re: [Ceph-maintainers] statically allocated uid/gid for ceph
Date: Thu, 14 May 2015 07:53:45 -0600 [thread overview]
Message-ID: <5554A8E9.1050501@redhat.com> (raw)
In-Reply-To: <55549206.3040008@suse.com>
On 05/14/2015 06:16 AM, Tim Serong wrote:
> The above should have no impact on other distros where a fixed UID/GID
> is already set in the package.
>
> Does this sound viable?
This plan sounds fine to me.
- Ken
> [1] Or, possibly, it should force both UID and GID to the same number,
> meaning we only need one argument, say --ceph-uidgid?
Sure, sounds good.
next prev parent reply other threads:[~2015-05-14 13:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1412061245410.18213@cobra.newdream.net>
[not found] ` <5488919E.4090109@redhat.com>
2014-12-10 18:48 ` [Ceph-maintainers] statically allocated uid/gid for ceph Sage Weil
2014-12-11 2:07 ` Tim Serong
2014-12-11 22:47 ` John Spray
2015-04-14 1:02 ` Sage Weil
2015-04-14 1:05 ` Sage Weil
2015-04-14 4:03 ` Tim Serong
2015-04-14 15:21 ` Sage Weil
2015-04-14 16:12 ` Ken Dreyer
2015-04-15 17:14 ` Gaudenz Steinlin
2015-04-27 9:56 ` Tim Serong
2015-04-27 11:29 ` HEWLETT, Paul (Paul)** CTR **
2015-04-28 5:00 ` Tim Serong
2015-04-27 16:02 ` Sage Weil
2015-05-14 12:16 ` Tim Serong
2015-05-14 13:53 ` Ken Dreyer [this message]
2015-05-14 16:08 ` Sage Weil
[not found] ` <CAANLjFpgivwxMhFLy4OcCxnJ_k5ssORCUm2r+BgtU+LEPQmvPw@mail.gmail.com>
2015-05-14 16:20 ` Robert LeBlanc
2015-05-14 16:41 ` Sage Weil
2015-05-15 3:27 ` Tim Serong
2015-05-15 10:25 ` Colin Watson
2015-04-15 10:32 ` Tim Serong
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=5554A8E9.1050501@redhat.com \
--to=kdreyer@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-maintainers@ceph.com \
--cc=cjwatson@debian.org \
--cc=gaudenz@debian.org \
--cc=osynge@suse.com \
--cc=sweil@redhat.com \
--cc=timm@fnal.gov \
--cc=tserong@suse.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.