On Mon, 2015-06-01 at 13:02 +0200, Michael Schwendt wrote: […] > Well, a few typical first steps would be to test with SELinux enforcing=0, > to check "rpm -V systemd", to "strace systemctl" and see which files/dirs > it tries to open. Definitely an SELinux problem. "setenforce 0" and the trouble goes away. Which would seem to indicate that the update to 220 is the root of the problem? -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@xxxxxxxxx 41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@xxxxxxxxxxxxx London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
Attachment:
signature.asc
Description: This is a digitally signed message part
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
