Re: Autostart service (systemd)
Well, but the problem is still there - it's just that Selinux is no longer blocking access. If you know which file Selinux is complaining about, you could do a 'restorecon' on it as root. Alternatively, you could have Selinux do a system relabel but that takes a very long time at the next boot. In either case, I'd fix the problem and set Selinux back to enforcing. If you opt for the relabel and reboot, there will be a point where it looks like your system got stuck/hung - it ISN'T. One of my systems takes almost a half hour to relabel.
Change - the only constant.