Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

A "BUSERROR" notify message is documented but not implemented #6073

Closed
mvduin opened this issue Jun 1, 2017 · 1 comment · Fixed by #33430
Closed

A "BUSERROR" notify message is documented but not implemented #6073

mvduin opened this issue Jun 1, 2017 · 1 comment · Fixed by #33430
Labels
pid1 RFE 🎁 Request for Enhancement, i.e. a feature request

Comments

@mvduin
Copy link
Contributor

mvduin commented Jun 1, 2017

Submission type

  • Documentation error

systemd version the issue has been seen with

git master

Both sd-daemon.h and the sd_notify manpage mention a "BUSERROR=..." notify message, however no such message is actually implemented.
@poettering
Copy link
Member

Yeah, we should collect that and show it.

@poettering poettering added pid1 RFE 🎁 Request for Enhancement, i.e. a feature request labels Jun 12, 2017
YHNdnzj added a commit to YHNdnzj/systemd that referenced this issue Jun 20, 2024
@YHNdnzj
core/service: store BUSERROR= & VARLINKERROR= received through notifi…
61822ab 
…cation

Closes systemd#6073
YHNdnzj added a commit to YHNdnzj/systemd that referenced this issue Jun 20, 2024
@YHNdnzj
core/service: store BUSERROR= & VARLINKERROR= received through notifi…
564e0bb 
…cation

Closes systemd#6073
@poettering poettering mentioned this issue Jun 20, 2024
Merged
poettering added a commit to poettering/systemd that referenced this issue Jun 20, 2024
@poettering
busctl: send BUSERROR= to caller via sd_notify() protocol
0663422 
varlinkctl has this nice feature that it sends the varlink error it gets
via sd_notify() to the caller. With systemd#33430 ths information is collected
and exposed in "systemctl status".

Let's make sure we can provide the same in busctl: also propagate errors
the same way.

With this and systemd#33430 we can comprehensively close systemd#6073
poettering added a commit to poettering/systemd that referenced this issue Jun 20, 2024
@poettering
busctl: send BUSERROR= to caller via sd_notify() protocol
801dad8 
varlinkctl has this nice feature that it sends the varlink error it gets
via sd_notify() to the caller. With systemd#33430 ths information is collected
and exposed in "systemctl status".

Let's make sure we can provide the same in busctl: also propagate errors
the same way.

With this and systemd#33430 we can comprehensively close systemd#6073
@poettering poettering mentioned this issue Jun 20, 2024
Closed
YHNdnzj added a commit to YHNdnzj/systemd that referenced this issue Jun 20, 2024
@YHNdnzj
core/service: store BUSERROR= & VARLINKERROR= received through notifi…
702c0c2 
…cation

Closes systemd#6073
YHNdnzj pushed a commit to YHNdnzj/systemd that referenced this issue Jun 20, 2024
@poettering @YHNdnzj
busctl: send BUSERROR= to caller via sd_notify() protocol
852ea3f 
varlinkctl has this nice feature that it sends the varlink error it gets
via sd_notify() to the caller. With previous commits this information
is collected and exposed in "systemctl status".

Let's make sure we can provide the same in busctl: also propagate errors
the same way.

With this we can comprehensively close systemd#6073
YHNdnzj pushed a commit to YHNdnzj/systemd that referenced this issue Jun 20, 2024
@poettering @YHNdnzj
busctl: send BUSERROR= to caller via sd_notify() protocol
8ea9186 
varlinkctl has this nice feature that it sends the varlink error it gets
via sd_notify() to the caller. With previous commits this information
is collected and exposed in "systemctl status".

Let's make sure we can provide the same in busctl: also propagate errors
the same way.

With this we can comprehensively close systemd#6073
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pid1 RFE 🎁 Request for Enhancement, i.e. a feature request
Milestone
No milestone
2 participants
@mvduin @poettering