From b53374f99b619abd90a7c19d69d37a3298b084d5 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Thu, 16 Apr 2015 21:41:18 -0400 Subject: units: specify timeouts for more oneshot services Even trivial service occasionally get stuck, for example when there's a problem with the journal. There's nothing more annoying that looking at the cylon eye for a job with an infinite timeout. Use standard 90s for jobs that do some work, and 30s for those which should be almost instantenous. --- units/systemd-machine-id-commit.service.in | 1 + 1 file changed, 1 insertion(+) (limited to 'units/systemd-machine-id-commit.service.in') diff --git a/units/systemd-machine-id-commit.service.in b/units/systemd-machine-id-commit.service.in index dd765b6608..cccbf7b626 100644 --- a/units/systemd-machine-id-commit.service.in +++ b/units/systemd-machine-id-commit.service.in @@ -19,3 +19,4 @@ ConditionPathIsMountPoint=/etc/machine-id Type=oneshot RemainAfterExit=yes ExecStart=@rootlibexecdir@/systemd-machine-id-commit +TimeoutSec=30s -- cgit v1.2.3-54-g00ecf