Bug#897654: libpam-systemd: "Failed to create session: No such process"

Michael Biebl biebl at debian.org
Fri May 4 17:02:09 BST 2018


Control: forcemerge 892585 -1
Am 04.05.2018 um 17:02 schrieb Michael Biebl:
> Am 03.05.2018 um 23:56 schrieb Michael Gold:
>> On Thu, May 03, 2018 at 23:42:34 +0200, Michael Biebl wrote:
>>> Am 03.05.2018 um 23:12 schrieb Michael Gold:
>>>> Is this problem already tracked?
>>> I'd say this is a duplicate of #892585
>>
>> Agreed.
> 
> That bug report mentioned, that dropping gid= was sufficient for him to
> fix the issue.

I guess you have two options here:
Either drop gid=4 from your mount flags or you add
SupplementaryGroups=adm to systemd-logind.service

Why adm is a suitable group for that purpose is not clear to me, but
that's besides the point.
https://wiki.archlinux.org/index.php/Security#hidepid suggests to use a
dedicated group like proc which makes more sense to me.

Anyway, this really seems to simply be a local (mis)configuration issue.

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180504/df7fd042/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list