Your message dated Sat, 9 Sep 2017 10:08:51 -0300
with message-id
<caafdzj-xus-kc3l5la-bh89fo+vswa1hrcks75w6y2mk-4y...@mail.gmail.com>
and subject line Re: Bug#856924: systemd: on WorkingDirectory not existing,
some weird log about CHROOT is generated
has caused the Debian Bug report #856924,
regarding systemd: on WorkingDirectory not existing, some weird log about
CHROOT is generated
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
856924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856924
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
Best
-- Package-specific info:
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to it_IT.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.115
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.11.0-2
ii libaudit1 1:2.6.7-1
ii libblkid1 2.29.1-1
ii libc6 2.24-9
ii libcap2 1:2.25-1
ii libcryptsetup4 2:1.7.3-3
ii libgcrypt20 1.7.6-1
ii libgpg-error0 1.26-2
ii libidn11 1.33-1
ii libip4tc0 1.6.0+snapshot20161117-5
ii libkmod2 24-1
ii liblz4-1 0.0~r131-2+b1
ii liblzma5 5.2.2-1.2+b1
ii libmount1 2.29.1-1
ii libpam0g 1.1.8-3.5
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.6-3
ii libsystemd0 232-19
ii mount 2.29.1-1
ii util-linux 2.29.1-1
Versions of packages systemd recommends:
ii dbus 1.10.16-1
ii libpam-systemd 232-19
Versions of packages systemd suggests:
ii policykit-1 0.105-17
pn systemd-container <none>
pn systemd-ui <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.127
ii udev 232-19
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 233-1
On Sat, Sep 9, 2017 at 6:43 AM, Michael Biebl <[email protected]> wrote:
> On Mon, 6 Mar 2017 09:48:11 -0300 Felipe Sateler <[email protected]>
> wrote:
> > On Mon, Mar 6, 2017 at 7:32 AM, Salvo Tomaselli <[email protected]>
> 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.
>
Agreed, this is good enough. I don't have ideas for better wording, so
closing is fine.
--
Saludos,
Felipe Sateler
--- End Message ---
