[systemd-devel] 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file
Lennart Poettering
lennart at poettering.net
Mon May 18 10:40:48 PDT 2015
On Wed, 29.04.15 19:34, nusenu (nusenu at openmailbox.org) wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hi,
>
> I'm running into a problem with systemd's hardening features
> ReadOnlyDirectories and ReadWriteDirectories *when* using them in
> multi-instance service files - temp. workaround was to disable them [1].
>
> - - that the service works fine *with* these hardening features enabled
> in a single instance service file
> - - I'm not using the %i placeholder in the ReadWriteDirectories paths
>
> Error message:
>
> Failed at step NAMESPACE spawning /usr/bin/tor: No such file or directory
> service: main process exited, code=exited, status=226/NAMESPACE
Any chance you can retry to reproduce this with "strace -p1 -o
/tmp/log -f -s500" so that we can see what precisely is failing there?
Lennart
--
Lennart Poettering, Red Hat
More information about the systemd-devel
mailing list