diff options
| author | Colin Guthrie <colin@mageia.org> | 2014-01-14 13:50:23 +0000 |
|---|---|---|
| committer | Colin Guthrie <colin@mageia.org> | 2014-01-14 20:51:05 +0000 |
| commit | 341ee9fe5e9810a8cc1a7d7156da0158f78dce68 (patch) | |
| tree | dc8138e9ec90bf1d44547f9ebaaf93315fa4784c /ChangeLog | |
| parent | 2fcb32d7734ceb9e1aec503dbb3fe79a5f656375 (diff) | |
| download | drakx-341ee9fe5e9810a8cc1a7d7156da0158f78dce68.tar drakx-341ee9fe5e9810a8cc1a7d7156da0158f78dce68.tar.gz drakx-341ee9fe5e9810a8cc1a7d7156da0158f78dce68.tar.bz2 drakx-341ee9fe5e9810a8cc1a7d7156da0158f78dce68.tar.xz drakx-341ee9fe5e9810a8cc1a7d7156da0158f78dce68.zip | |
services.pm: Use no-reload mode when interacting with systemd.
Basically, there seems to be an issue right now if we do lots of reloads.
It seems to be somewhat racy and systemd gets generally confused when we
do this during boot (which we do) and trigger a reload. The reload isn't
strictly needed, as we do also explicitly start the services we enable
(with --no-block so that we don't cause a deadlock) so all *should* be
99% OK. Using it at runtime might mean we don't have fully up-to-date
enablement status, but being able to boot wins at the moment.
Diffstat (limited to 'ChangeLog')
0 files changed, 0 insertions, 0 deletions