From 74ac3cbd509de2f5995542aa5db39328e8cbd22a Mon Sep 17 00:00:00 2001 From: Matthew Miller Date: Tue, 31 Aug 2010 00:17:56 +0200 Subject: manager: rename 'maintenance' state to 'failed' to avoid user confusion https://bugzilla.redhat.com/show_bug.cgi?id=614619 --- man/systemd.unit.xml | 30 ++++++++++++++++-------------- 1 file changed, 16 insertions(+), 14 deletions(-) (limited to 'man/systemd.unit.xml') diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 250989fe0f..3bc5d3c66f 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -418,8 +418,9 @@ Lists one or more units that are activated when this - unit fails (i.e. enters maintenance - state). + unit enters the + 'failed' + state. @@ -552,22 +553,23 @@ time. If this time limit is reached the job will be cancelled, the unit however will not change state or even - enter maintenance mode. This value - defaults to 0 (job timeouts disabled), - except for device units. NB: this - timeout is independent from any - unit-specific timeout (for example, - the timeout set with + enter the 'failed' + mode. This value defaults to 0 (job + timeouts disabled), except for device + units. NB: this timeout is independent + from any unit-specific timeout (for + example, the timeout set with Timeout= in service - units) as the job timeout has no effect - on the unit itself, only on the job - that might be pending for it. Or in - other words: unit-specific timeouts + units) as the job timeout has no + effect on the unit itself, only on the + job that might be pending for it. Or + in other words: unit-specific timeouts are useful to abort unit state changes, and revert them. The job timeout set with this option however - is useful to abort only the job waiting - for the unit state to change. + is useful to abort only the job + waiting for the unit state to + change. -- cgit v1.2.3-54-g00ecf