If it's ybbind that's causing issues, then chances are it's related to
the NSS setup, i.e. /etc/nsswitch.conf and other related config specific
to Yellow Pages stuff (I forget what they are as it's been > 10years
since I used it!)
It could be the NSS system is asking for user/group info via YP
Is this an expected behavior?
Debian 9 with systemd 232-25+deb9u1
Apache is running as user wp_user.
After logging in and logging out via sftp as user wp_user - systemd
kills apache process.
Feb 1 10:58:25 shop systemd: pam_unix(systemd-user:session): session
opened for user wp_user by
Hello, Michal.
After some trial an error I was able to find the culprit: the ypbind daemon.
- If I have it enabled, then it seems to me that, for some reason,
systemd can not take ownership of the dbus names (/me not sure if that
is the correct terminology).
- If I leave it disabled, then the
On Thu, Feb 1, 2018 at 1:32 PM, Simon Becks wrote:
> Is this an expected behavior?
>
> Debian 9 with systemd 232-25+deb9u1
>
> Apache is running as user wp_user.
>
> After logging in and logging out via sftp as user wp_user - systemd
> kills apache process.
>
> Feb 1
01.02.2018 15:08, Mantas Mikulėnas пишет:
>>
>
> For users outside the "system account" UID range (usually 1–999), a logout
> will cause systemd to clean up remaining "junk" such as SysV IPC resources.
Where is it documented?
___
systemd-devel mailing
01.02.2018 22:00, Mike Gilbert пишет:
> On Thu, Feb 1, 2018 at 1:42 PM, Andrei Borzenkov wrote:
>> 01.02.2018 15:08, Mantas Mikulėnas пишет:
>>>
>>> For users outside the "system account" UID range (usually 1–999), a logout
>>> will cause systemd to clean up remaining
On Thu, Feb 1, 2018 at 1:42 PM, Andrei Borzenkov wrote:
> 01.02.2018 15:08, Mantas Mikulėnas пишет:
>>>
>>
>> For users outside the "system account" UID range (usually 1–999), a logout
>> will cause systemd to clean up remaining "junk" such as SysV IPC resources.
>
>
> Where