Yes, We really want the protection afforded our servers with SELInux,
but then there are all these policies to apply when we need to open
things up some.
Very challenging for sure.
On 03/06/2017 09:16 AM, David B Snyder wrote:
Thanks, this seems to have worked!
I guess I need to learn
Thanks, this seems to have worked!
I guess I need to learn about SELinux now. :)
On 03/05/2017 06:04 PM, Robert Moskowitz wrote:
Are you running SELinux?
Have you done the needed:
chcon -R -t httpd_sys_content_rw_t /diretory
commands?
On 03/05/2017 05:48 PM, David B Snyder wrote:
I am
I have tried.
I don't have iname,so I have tried setting up each directory.
/ works (gets the directory listing)
/mnt works
/mnt/Workspace doesn't work 403 Forbidden, yet I see no difference in
the permissions, they are all r-x for group and world. That is where it
crosses file systems.
Are you running SELinux?
Have you done the needed:
chcon -R -t httpd_sys_content_rw_t /diretory
commands?
On 03/05/2017 05:48 PM, David B Snyder wrote:
I am trying to set up httpd across several file systems on a Fedora 25
Linux
system, and I'm doing something wrong.
I haven't succeeded
On Sun, Mar 5, 2017 at 5:48 PM, David B Snyder wrote:
> Thanks for any advice
You need to check every component of the path, such as the output of
namei -m /mnt/Workspace/snyder/www/index.html
--
Eric Covener
cove...@gmail.com
I am trying to set up httpd across several file systems on a Fedora 25 Linux
system, and I'm doing something wrong.
I haven't succeeded in getting httpd to serve pages across the mounted
file systems.
example errors:
[Sun Mar 05 13:31:50.628070 2017] [core:error] [pid 1001] (13)Permission