Bug#856924: systemd: on WorkingDirectory not existing, some weird log about CHROOT is generated

Michael Biebl biebl at debian.org
Sat Sep 9 10:43:53 BST 2017

On Mon, 6 Mar 2017 09:48:11 -0300 Felipe Sateler <fsateler at debian.org>
> On Mon, Mar 6, 2017 at 7:32 AM, Salvo Tomaselli <tiposchi at tiscali.it> wrote:

> > WorkingDirectory=/does/not/exist

> >
> > And when I try to start it I obtain
> > lala.service: Failed at step CHROOT spawning /bin/sh: No such file or directory
> >
> > which makes it seem like /bin/sh is not found, when actually the issue is that
> > WorkingDirectory doesn't exist.
> >
> > Perhaps a log message related to the actual error would be of more use.
> This was improved in 233:
> test.service: Failed at step CHDIR spawning /bin/sh: No such file or directory
> But I think this is still a bit confusing.

I think the error message is not brilliant, but good enough to consider
this issue fixed.
Felipe, if you still want to see this improved, please forward it
upstream. Otherwise I'm going to close this bug report.


Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170909/5e15416e/attachment-0001.sig>

More information about the Pkg-systemd-maintainers mailing list