From: Joonas Niilola <juippis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] UID/GID assignment for kibana
Date: Fri, 20 Sep 2019 19:36:11 +0300 [thread overview]
Message-ID: <d9eb2795-f6d1-9ba5-97aa-bc5253bdbb9d@gentoo.org> (raw)
In-Reply-To: <CAG6MAzSD_9Ct0fSG6792=OK1iR1efN2pr6F6wn5i2+nSBo0=CQ@mail.gmail.com>
Hey,
On 9/20/19 7:12 PM, Tomas Mozes wrote:
> Hi there,
> while trying to implement glep 81 for kibana I found out that Arch
> Linux uses uid 183 for it, but it's taken by qmail.eclass. Should a
> new uid/gid be taken or it's safe to assume no one will mix kibana
> with qmail?
>
>
I can't find this info anywhere. There's a pull request currently open
for acct-*/qmail stuff, that seems to reserve 200+ for it (like shown in
uid-gid.txt). Nothing seems to reserve 183 as far as I can tell?
- https://gitweb.gentoo.org/data/api.git/tree/files/uid-gid.txt
-
https://github.com/gentoo/gentoo/pull/12898/files#diff-bb8c77449e92c212844f37fc9a56e12aL105
-- juippis
next prev parent reply other threads:[~2019-09-20 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 16:12 [gentoo-dev] UID/GID assignment for kibana Tomas Mozes
2019-09-20 16:36 ` Joonas Niilola [this message]
2019-09-20 16:43 ` Tomas Mozes
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=d9eb2795-f6d1-9ba5-97aa-bc5253bdbb9d@gentoo.org \
--to=juippis@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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