From: Willem Jan Withagen <wjw@digiware.nl>
To: Brad Hubbard <bhubbard@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: UID/GID for ceph user and group
Date: Mon, 20 Feb 2017 12:12:12 +0100 [thread overview]
Message-ID: <ec3a4383-fb69-c13c-58d8-baa00ed24aa3@digiware.nl> (raw)
In-Reply-To: <CAF-wwdEhot7H6Oua5bNX66=xay8y5CAp3w4i5LVYDE9ALdJbPQ@mail.gmail.com>
On 20-2-2017 11:49, Brad Hubbard wrote:
>>> On my centos7 box they are not defined when I installed the ceph package?
>
> It was this statement that concerned me. Wondering why the ceph
> user/group wasn't created during your CentOS install?
Good argument, but now you put your thumb on it.
Ceph is not installed on that CentOS VM, it is just for builds when I
can not figure out why Jenkins is giving me pains with a PR.
And to avoid pollution in the info, ceph is natively not installed in
the VM.
But then again on our cluster running Ubuntu 14.04.5 LTS it isn't there
either. But I'd have to ask the administrators as to why that is.
Seems daemons are running as root.
--WjW
> On Mon, Feb 20, 2017 at 7:53 PM, Willem Jan Withagen <wjw@digiware.nl> wrote:
>> On 20-2-2017 07:07, Brad Hubbard wrote:
>>> On Fri, Feb 17, 2017 at 1:46 AM, Willem Jan Withagen <wjw@digiware.nl> wrote:
>>>> Hi,
>>>>
>>>> Is there a typical uid/gid that is selected on oterh platforms to assign
>>>> to ceph:ceph?
>>>
>>> https://github.com/ceph/ceph/blob/master/ceph.spec.in#L970
>>>
>>> I wonder if that should be "%if 0%{?rhel} || 0%{?fedora} || 0%{?centos}" ?
>>>
>>> Seems odd you'd be the first to notice though?????
>>>
>>>>
>>>> On my centos7 box they are not defined when I installed the ceph package?
>>
>> This is/was for my FreeBSD ceph port....
>> And it seems that there is a bit of consensus on 167 IF IDs need to be <
>> 1000. Which is the case for preassigned UID/GIDs on FreeBSD.
>>
>> So for now I took 167:167, which was still free.
>>
>> Thanx,
>> --WjW
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
next prev parent reply other threads:[~2017-02-20 11:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 15:46 UID/GID for ceph user and group Willem Jan Withagen
2017-02-20 6:07 ` Brad Hubbard
2017-02-20 9:53 ` Willem Jan Withagen
2017-02-20 10:49 ` Brad Hubbard
2017-02-20 11:12 ` Willem Jan Withagen [this message]
2017-02-20 11:20 ` Brad Hubbard
2017-02-20 21:15 ` Nathan Cutler
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=ec3a4383-fb69-c13c-58d8-baa00ed24aa3@digiware.nl \
--to=wjw@digiware.nl \
--cc=bhubbard@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox