From 038193efa6c00e852110f17383ef2786136f4f81 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Wed, 5 Nov 2014 09:16:58 -0500 Subject: units: disable job timeouts For boot, we might kill fsck in the middle, with likely catastrophic consequences. On shutdown there might be other jobs, like downloading of updates for installation, and other custom jobs. It seems better to schedule an individual timeout on each one separately, when it is known what timeout is useful. Disable the timeouts for now, until we have a clearer picture of how we can deal with long-running jobs. --- units/reboot.target | 2 -- 1 file changed, 2 deletions(-) (limited to 'units/reboot.target') diff --git a/units/reboot.target b/units/reboot.target index 668b98d9e4..dec8f56796 100644 --- a/units/reboot.target +++ b/units/reboot.target @@ -12,8 +12,6 @@ DefaultDependencies=no Requires=systemd-reboot.service After=systemd-reboot.service AllowIsolate=yes -JobTimeoutSec=30min -JobTimeoutAction=reboot-force [Install] Alias=ctrl-alt-del.target -- cgit v1.2.3-54-g00ecf