Tom Horsley writes:

On Mon, 14 Jan 2013 08:32:19 -0500
Sam Varshavchik wrote:

> … appears to be Apache. After installing the most recent systemd update:
>
> systemd[1429]: Failed at step NAMESPACE spawning /usr/sbin/httpd: Operation
> not permitted

I just installed updates (and rebooted) this morning and apache seems to be running
fine on my desktop. I've got systemd-44-23.fc17.x86_64

Yeah, some of my other machines seems to have survived. But all I know, is that on a stripped down, headless box, this update broke Apache, until I took out PrivateTmp out of httpd.service. Only systemd was updated, apache wasn't. That's all I can figure out for now. The error message text wasn't very helpful, and googling it around found a bunch of references to PrivateTmp, so I took it out, and systemctl start httpd.service worked. Put it back, systemd refuses to start it, take it out, it works.

Attachment: pgpOBqFwswcuO.pgp
Description: PGP signature

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Reply via email to