]> git.ipfire.org Git - thirdparty/systemd.git/commit
projects / thirdparty / systemd.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: d4341b7) | patch
manager: fix confusion when to send READY=1
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Wed, 3 Nov 2021 10:22:28 +0000 (11:22 +0100)
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Wed, 3 Nov 2021 10:32:31 +0000 (11:32 +0100)
commit028f7d3ac6570ddf41a34ba9741798ef777ddacc
treeaaf47204acd954a273fee9c9b9bb6780e85ff9d6tree | snapshot
parentd4341b76d07fd7117a36b2f4e4b41cab41f0cf14commit | diff
manager: fix confusion when to send READY=1

I got the logic reversed in 6d9326595592f98e8126eacb4176acd8c3516d5c.
Let's just remove the conditionalization of the status message: if we're
sending something, we might just as well always attach READY=1, the extra
few bytes don't make much of a difference.

FWIW, it seems that this bug didn't cause problems, probably because we'd send
READY=1 either from user_manager_send_ready() or from a later call to
manager_send_ready().
src/core/manager.c diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.