https://bugzilla.novell.com/show_bug.cgi?id=856798 https://bugzilla.novell.com/show_bug.cgi?id=856798#c0 Summary: systemd's PrivateTmp option breaks services if /var/tmp is symlinked to /tmp Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Yarny@public-files.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 My system has /tmp on a separate filesystem, and /var/tmp is a symlink to /tmp. Starting with openSUSE 13.1, this breaks apache2.service (and possibly more services where PrivateTmp=yes is set in the service file). Starting apache2.service yields:

Dec 25 18:19:55 82a7090 systemd[1194]: Failed at step NAMESPACE spawning /usr/sbin/start_apache2: Operation not permitted Dec 25 18:19:55 82a7090 systemd[1]: apache2.service: main process exited, code=exited, status=226/NAMESPACE Dec 25 18:19:55 82a7090 systemd[1196]: Failed at step NAMESPACE spawning /usr/sbin/start_apache2: Operation not permitted Dec 25 18:19:55 82a7090 systemd[1]: apache2.service: control process exited, code=exited status=226 Dec 25 18:19:55 82a7090 systemd[1]: Failed to start The Apache Webserver.

Reproducible: Always Steps to Reproduce: 1. Make /var/tmp a symlink to /tmp 2. Start apache2.service My current workaround is an rbind mount of /tmp to /var/tmp. Here is a similar report from Fedora: <https://bugzilla.redhat.com/835131> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.