[systemd-devel] 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

[Lennart Poettering]

On Mon, 18.05.15 18:31, nusenu (nusenu at openmailbox.org) wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> >> 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?
> 
> looks like it works out of the box now! :)
> 
> Since then systemd got updated, but I didn't see anything related in
> debians changelog:
> http://metadata.ftp-master.debian.org/changelogs//main/s/systemd/systemd_215-17_changelog

If it works now I would let it rest. Feel free to raise this here
again should it reappear.

Thanks,

Lennart

-- 
Lennart Poettering, Red Hat