EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #07342
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] CentOS / SELinux
- To: "'eprints-tech@ecs.soton.ac.uk'" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] CentOS / SELinux
- From: John Salter <J.Salter@leeds.ac.uk>
- Date: Thu, 28 Jun 2018 09:34:36 +0000
Hi All, There's just been an exchange on the eprints-uk-user-group mailing list, where someone was having issues getting EPrints up and running. The root cause was SELinux. On this page: http://wiki.eprints.org/w/Installing_EPrints_on_RHEL/Fedora/CentOS#Using_SELinux
there is some advice - but it doesn't seem to cover any of the directories that things like the Bazaar would need access to (e.g. ~/lib/plugins/). It also doesn't include [eprintspath]/archives/[repoid]/html/ - which means summary-pages fail to be written when an http request causes them to be regenerated. This message (from 2015)
http://threader.ecs.soton.ac.uk/lists/eprints_tech/21145.html suggests granting r/w permission for the whole eprints install directory (/usr/share/eprints/). Is this the most sensible option? Should e.g. ~/perl_lib, ~/bin, ~/cgi be more locked down? Cheers, John PS There is also this note:
http://wiki.eprints.org/w/Troubleshooting#A_Note_on_SELinux - but that references EPrints2 - so probably a little outdated. |
- Follow-Ups:
- [EP-tech] CentOS / SELinux
- From: John Salter <J.Salter@leeds.ac.uk>
- [EP-tech] CentOS / SELinux
- References:
- [EP-tech] CentOS / SELinux
- From: John Salter <J.Salter@leeds.ac.uk>
- [EP-tech] CentOS / SELinux
- Prev by Date: Re: [EP-tech] Sending out Error Statuses with Error codes
- Next by Date: Re: [EP-tech] CentOS / SELinux
- Previous by thread: [EP-tech] EPrints/CRIS
- Next by thread: [EP-tech] DOI handling in orcid_support_advance
- Index(es):