From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com>, "Joshua D(dot) Drake" <linuxhiker(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PSA: Systemd will kill PostgreSQL |
Date: | 2016-07-11 09:49:44 |
Message-ID: | B969A89B16D6C12AEA554694@eje.land.credativ.lan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
--On 11. Juli 2016 13:25:51 +0800 Craig Ringer <craig(at)2ndquadrant(dot)com>
wrote:
> Perhaps by uid threshold in login.defs?
systemd's configure.ac has this:
AC_ARG_WITH(system-uid-max,
AS_HELP_STRING([--with-system-uid-max=UID]
[Maximum UID for system users]),
[SYSTEM_UID_MAX="$withval"],
[SYSTEM_UID_MAX="`awk 'BEGIN { uid=999 } /^\s*SYS_UID_MAX\s+/ {
uid=$2 } END { print uid }' /etc/login.defs 2>/dev/null || echo 999`"])
so yes, it's the definition from there.
> But then what happens for people
> who're managing users via a directory, who need to avoid conflicting with
> host-local UIDs, but also need some of those users to have systemd
> "system user" like behaviour?
We had this in the past in some setups and this would add another reason
for unexpected headaches...
--
Thanks
Bernd
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2016-07-11 10:01:40 | Re: BUG #14230: Wrong timeline returned by pg_stop_backup on a standby |
Previous Message | Kyotaro HORIGUCHI | 2016-07-11 08:10:11 | Re: asynchronous and vectorized execution |