Use config_parse_sec_fix_0() also for JobRunningTimeoutSec
2d79a0bbb9did that for TimeoutSec=,89beff89eddid that for JobTimeoutSec=, and0004f698dfdid that for x-systemd.device-timeout=. But after parsing x-systemd.device-timeout=xxx we write it out as JobRunningTimeoutSec=xxx. Two options: - write out JobRunningTimeoutSec=<a very big number>, - change JobRunningTimeoutSec= to behave like the other options. I think it would be confusing for JobRunningTimeoutSec= to have different syntax then TimeoutSec= and JobTimeoutSec=, so this patch implements the second option. Fixes #6264, https://bugzilla.redhat.com/show_bug.cgi?id=1462378.
This commit is contained in:
@@ -194,7 +194,7 @@ Unit.OnFailureIsolate, config_parse_job_mode_isolate, 0,
|
||||
Unit.IgnoreOnIsolate, config_parse_bool, 0, offsetof(Unit, ignore_on_isolate)
|
||||
Unit.IgnoreOnSnapshot, config_parse_warn_compat, DISABLED_LEGACY, 0
|
||||
Unit.JobTimeoutSec, config_parse_sec_fix_0, 0, offsetof(Unit, job_timeout)
|
||||
Unit.JobRunningTimeoutSec, config_parse_sec, 0, offsetof(Unit, job_running_timeout)
|
||||
Unit.JobRunningTimeoutSec, config_parse_sec_fix_0, 0, offsetof(Unit, job_running_timeout)
|
||||
Unit.JobTimeoutAction, config_parse_emergency_action, 0, offsetof(Unit, job_timeout_action)
|
||||
Unit.JobTimeoutRebootArgument, config_parse_unit_string_printf, 0, offsetof(Unit, job_timeout_reboot_arg)
|
||||
Unit.StartLimitIntervalSec, config_parse_sec, 0, offsetof(Unit, start_limit.interval)
|
||||
|
||||
Reference in New Issue
Block a user