[systemd-bugs] [Bug 80749] New: RFE: NOTIFY_SOCKET ERRNO is not implemented
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Jul 1 00:46:21 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=80749
Priority: medium
Bug ID: 80749
Assignee: systemd-bugs at lists.freedesktop.org
Summary: RFE: NOTIFY_SOCKET ERRNO is not implemented
QA Contact: systemd-bugs at lists.freedesktop.org
Severity: normal
Classification: Unclassified
OS: All
Reporter: majopela at redhat.com
Hardware: Other
Status: NEW
Version: unspecified
Component: general
Product: systemd
Description of problem:
NOTIFY_SOCKET specification of systemd [1] describes the ERRNO argument,
that would allow for passing error numbers for 'systemctl status' return,
but it's not implemented [2],[3]
I discovered it during the design of this specifications: [4]
I'm am proposing a new dbus field for this message (ERRNO, along with PID,
Code, Status).
Initially I thought of using the ExecStatus code, but this is overwritten at
final daemon exit.
Also, I think this message has potential [4] to be used as a complement
to the status string which can be passed via NOTIFY_SOCKET, but as a
numeric error when a daemon is having any trouble and running in degraded
mode. Specially when using some HA solution like pacemaker and we need to
notify that the service is degraded, but we don't want to bring the service
down to communicate an exit code.
[1] http://www.freedesktop.org/software/systemd/man/sd_notify.html
[2]
http://cgit.freedesktop.org/systemd/systemd/tree/src/core/service.c?id=194bbe33382f5365be3865ed1779147cb#n3201
[3]
http://cgit.freedesktop.org/systemd/systemd/tree/src/systemctl/systemctl.c?id=194bbe33382f5365be3865ed1779147cb#n2882
[4]
http://docs-draft.openstack.org/48/97748/1/check/gate-oslo-specs-docs/c4a464e/doc/build/html/
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140701/12607a64/attachment.html>
More information about the systemd-bugs
mailing list