[systemd-bugs] [Bug 89864] New: Error message when working directory does not exist can be misleading

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 89864
           Summary: Error message when working directory does not exist
                    can be misleading
           Product: systemd
           Version: unspecified
          Hardware: All
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: rbarlow at redhat.com
        QA Contact: systemd-bugs at lists.freedesktop.org

If the WorkingDirectory directive in a unit is configured for a directory that
does not exist, the error message that is printed is a little confusing to
read.

For example, we have a systemd service template[0] that sets the working
directory to /var/run/pulp/. If that folder does not exist when the unit is
started, this is the error message that is printed:

Failed at step CHDIR spawning /usr/bin/celery: No such file or directory

I say "can be" misleading, because I see that technically it is saying that
CHDIR failed *when* spawning /usr/bin/celery (which is correct). Unfortunately,
it might read to some people[1] that /usr/bin/celery didn't exist, which can be
confusing. I think it might be helpful if it instead told me that it could not
find /var/run/pulp. Maybe something like this would be nice:

While spawning /usr/bin/celery, failed to chdir /var/run/pulp: No such file or
directory

Thanks, and let me know if I can provide any more information!

[0]
https://github.com/pulp/pulp/blob/e6ea3131796df60de3f7e3b98acc2ef108f517f7/server/pulp/server/async/manage_workers.py#L27-L38
[1] Like me ☺

-- 
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/20150401/71ac5acd/attachment.html>