Bug#813702: systemd: Oneshot service doesn't get killed after timeout.

On Fri, 18 Mar 2016 21:39:20 +0100 Michael Biebl wrote: > Am 18.03.2016 um 20:52 schrieb Greg Edwards: > > This is the upstream commit in v217 that fixes this bug: > > > > commit 21b2ce39d4038cd6176394836fdcfb7fba63f424 > > Author: Lennart Poettering > > Date: Thu Aug 21 18:01:22 2014 +0200 > > >

Bug#813702: systemd: Oneshot service doesn't get killed after timeout.

Am 18.03.2016 um 20:52 schrieb Greg Edwards: > This is the upstream commit in v217 that fixes this bug: > > commit 21b2ce39d4038cd6176394836fdcfb7fba63f424 > Author: Lennart Poettering > Date: Thu Aug 21 18:01:22 2014 +0200 > > service: use the right timeout for stop processes we f

Bug#813702: systemd: Oneshot service doesn't get killed after timeout.

Hi Greg Am 18.03.2016 um 20:52 schrieb Greg Edwards: > This is the upstream commit in v217 that fixes this bug: > > commit 21b2ce39d4038cd6176394836fdcfb7fba63f424 > Author: Lennart Poettering > Date: Thu Aug 21 18:01:22 2014 +0200 > > service: use the right timeout for stop proce

Bug#813702: systemd: Oneshot service doesn't get killed after timeout.

This is the upstream commit in v217 that fixes this bug: commit 21b2ce39d4038cd6176394836fdcfb7fba63f424 Author: Lennart Poettering Date: Thu Aug 21 18:01:22 2014 +0200 service: use the right timeout for stop processes we fork Could we get this patch added to a future systemd stab

Bug#813702: systemd: Oneshot service doesn't get killed after timeout.

I did test systemd v216 with no success. I had better luck with v217 which fix the issue.

Bug#813702: systemd: Oneshot service doesn't get killed after timeout.

Package: systemd Version: 215-17+deb8u3 Severity: normal Dear Maintainer, I have a custom systemd service which isn't killed after the default stop timeout, which prevent my system to shutdown properly. During shutdown, the screen displays "A stop job is running ... (X/no limit)" and then wait