[systemd-bugs] [Bug 89840] New: systemd.exec: add ExecFail option to start diagexec

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=89840

            Bug ID: 89840
           Summary: systemd.exec: add ExecFail option to start diagexec
           Product: systemd
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: alban.crequy at gmail.com
        QA Contact: systemd-bugs at lists.freedesktop.org

When starting a systemd unit file, it might print the following error based on
errno=ENOENT:

testscript[9959]: Failed at step EXEC spawning /testscript: No such file or
directory

This could mean /testscript is missing, or ld-2.19.so is missing or the
interpreter in the shebang is missing.

But the error message is not precise enough to know. The kernel does not give
more details when execve() fails with errno=ENOENT.

In order to print better error messages, we could have an option ExecFail in
the unit file:

ExecFail=/usr/bin/diagexec

It would start the diagnostic tool to guess why execve() returned ENOENT.

The code for diagexec is there:

https://github.com/coreos/rocket/blob/master/stage1/rootfs/diagexec/diagexec.c#L58

-- 
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/20150331/af1294a1/attachment.html>