Am 24.07.2016 um 17:47 schrieb Colin Watson:
> Compromise proposal: how about I make it do nothing if libpam-systemd is
> installed (e.g. "ConditionPathExists=!/usr/share/pam-configs/systemd",
> which is probably the simplest available check without needing to deal
> with multiarch paths), in
On Sun, Jul 24, 2016 at 01:38:25AM +0200, Michael Biebl wrote:
> I referenced in my other reply that the network.target ordering has just
> been added recently (in v230). So it is possible that previously there
> was still an issue on shutdown. This is fixed now.
Do you plan to update jessie with
Am 24.07.2016 um 17:47 schrieb Colin Watson:
> On Sun, Jul 24, 2016 at 01:38:25AM +0200, Michael Biebl wrote:
>> I referenced in my other reply that the network.target ordering has just
>> been added recently (in v230). So it is possible that previously there
>> was still an issue on shutdown.
On Sun, 2016-07-24 at 01:38 +0200, Michael Biebl wrote:
> It doesn't help for the non-systemd case and people who opt to not
> install recommends by default use a non-standard configuration, so
> it's
> imho ok if those need to also apply additional configuration in case
> of
> SSH. We should
Am 23.07.2016 um 12:29 schrieb Colin Watson:
> On Sat, Jul 23, 2016 at 01:35:04AM +0200, Michael Biebl wrote:
>> the addition of ssh-session-cleanup.service in the latest upload [1] is
>> imho a bad idea. It's an aweful hack and besides, it also kills your SSH
>> sessions on upgrades (thus
On Sat, 2016-07-23 at 11:29 +0100, Colin Watson wrote:
> While of course I have libpam-systemd installed on all my systems, I
> really don't want to depend on it; besides, the original report had
> people saying that they encountered occasional problems of sessions
> not
> being cleaned up even
On Sat, Jul 23, 2016 at 01:35:04AM +0200, Michael Biebl wrote:
> the addition of ssh-session-cleanup.service in the latest upload [1] is
> imho a bad idea. It's an aweful hack and besides, it also kills your SSH
> sessions on upgrades (thus severity RC).
>
> The proper fix is to use
Hi Colin
Am 23.07.2016 um 01:42 schrieb Michael Biebl:
> See also the relevant upstream commit:
>
> https://github.com/systemd/systemd/commit/8c856804780681e135d98ca94d08afe247557770
>
> This fix is part of v230. Before that, we had no proper ordering on
> shutdown, so it was indeed possible
See also the relevant upstream commit:
https://github.com/systemd/systemd/commit/8c856804780681e135d98ca94d08afe247557770
This fix is part of v230. Before that, we had no proper ordering on
shutdown, so it was indeed possible that some user sessions were not
properly terminated before the
9 matches
Mail list logo
