Re: SELinux problems
- Posted by jimcbrown (admin) Aug 22, 2015
- 2097 views
Has this issue been looked into? If so, was it determined that it can't/wont be fixed? Or am I experiencing a new problem much like an old one? On Fedora 22 with SELinux turned on, *eui* is causing this error today. I didn't notice this earlier in the week because my other VM with Fedora installed had SELinux turned off. For the moment, I've disabled SELinux on my VM so that I can continue my project for the next day or so as I explore if Euphoria is a good fit for this new project.
This should have been fixed, years ago, with the adoption of DEP-aware code and the new allocate_code() routine.
What's the exact command line you are passing to eui to get this error?
This type of error would be alarming for sysadmins considering Euphoria in the work place.
Agreed.
