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

[Felipe Sateler]

On Mon, Mar 6, 2017 at 7:32 AM, Salvo Tomaselli <tiposchi at tiscali.it> wrote:
> Package: systemd
> Version: 232-19
> Severity: normal
>
> Dear Maintainer,
> I have created a unit file like this
>
> [Unit]
> Description=lala
>
> [Service]
> WorkingDirectory=/does/not/exist
> ExecStart=/bin/sh -c "echo ciao"
>
> [Install]
> WantedBy=multi-user.target
>
> 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.

-- 

Saludos,
Felipe Sateler