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

2015-06-09 Thread Lennart Poettering
On Thu, 04.06.15 18:22, nusenu (nus...@openmailbox.org) wrote: 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

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

2015-05-18 Thread Lennart Poettering
On Wed, 29.04.15 19:34, nusenu (nus...@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.

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

2015-05-18 Thread nusenu
-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*

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

2015-05-18 Thread Lennart Poettering
On Mon, 18.05.15 18:31, nusenu (nus...@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