New *systemd* option: `RandomizedDelaySec`
This update introduces the `RandomizedDelaySec` option for *systemd* timers, which schedules an event to occur later by a random number of seconds. For example, setting the option to 10 will postpone the event by a random number of seconds between 0 and 10. The new option is useful for spreading workload over a longer time period to avoid several events executing at the same time.
+++ This bug was initially created as a clone of Bug #1303552 +++
Description of problem:
systemd 228 contains an option RandomSec= for systemd timer unit files.
Please backport this feature to Fedora 23.
Please see also bug #1074951 .
Version-Release number of selected component (if applicable):
--- Additional comment from Jan Synacek on 2016-02-01 07:20:58 EST ---
Backport 744c7693751830149ae78fdaf95c6c6f99d59f07 and 6f5d79986a9c98b9cacc83f865fed957e4e6e4e6.
--- Additional comment from Fedora Update System on 2016-02-01 09:51:26 EST ---
systemd-222-14.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-d3fc0f9415
--- Additional comment from Jan Synacek on 2016-02-01 09:52:25 EST ---
Note that the real option name is "RandomizedDelaySec=".
--- Additional comment from Fedora Update System on 2016-02-01 21:26:46 EST ---
systemd-222-14.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-d3fc0f9415
--- Additional comment from Fedora Update System on 2016-02-04 18:23:06 EST ---
systemd-222-14.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
pushed to staging ->
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.