28 Dec
2016
28 Dec
'16
9:45 p.m.
Robert Moskowitz wrote:
On 12/28/2016 01:53 PM, m.roth@5-cent.us wrote:
Robert Moskowitz wrote:
<SNIP>
Bang. I would suggest, at this point, that you might want to set selinux into permissive mode, so you'll get the error messages from it, and can work out fixes, but will let your system operate as you intend. setselinux 0
Note that this is *temporary*, and will revert on reboot. To make it permanent, you'd need to edit /etc/selinux/config.
Thanks, Mark, I was just getting around to that way of thinking.
The command, at least on my Centos7-arm system is
setenforce 0
Sorry. Clearly, there's too much blood in my caffeine stream....
A presto it works. So now to figure out what is wrong with SElinux on this image.
Good luck.
mark