diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2021-11-03 11:22:28 +0100 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2021-11-03 11:32:31 +0100 |
| commit | 028f7d3ac6570ddf41a34ba9741798ef777ddacc (patch) | |
| tree | aaf47204acd954a273fee9c9b9bb6780e85ff9d6 /src/coredump/coredumpctl.c | |
| parent | d4341b76d07fd7117a36b2f4e4b41cab41f0cf14 (diff) | |
| download | systemd-028f7d3ac6570ddf41a34ba9741798ef777ddacc.tar.gz | |
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().
Diffstat (limited to 'src/coredump/coredumpctl.c')
0 files changed, 0 insertions, 0 deletions