EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #07583
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Ubuntu 18 , mpm_prefork vs mpm_event
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Ubuntu 18 , mpm_prefork vs mpm_event
- From: Tomasz Neugebauer <Tomasz.Neugebauer@concordia.ca>
- Date: Fri, 23 Nov 2018 19:00:07 +0000
We are in the process of migrating our repository (3.3.12) from Ubuntu 12 to 18. We had to make a few changes/patches based on commits related to these issues: https://github.com/eprints/eprints/issues/236 https://github.com/eprints/eprints/issues/237 https://github.com/eprints/eprints/issues/214 https://github.com/eprints/eprints/issues/88
One remaining issue of confusion for me: apache refuses to start when we have mpm_event enabled, which is, from what I am told, the default for Ubuntu 18.04. When we switch to mpm_prefork,
it all seems to work as it should. Is anyone else running EPrints 3.3.12-3.3.16 on Ubuntu 18.04? Are you running with mpm_event enabled (you can check this with this command: apachectl -V | grep -i mpm). Any comments or advice on this? Should we be trying
to get this to work with mpm_event, or should we just use mpm_prefork, since that is working? Any advice or comments would be greatly appreciated. Tomasz |
- Follow-Ups:
- [EP-tech] Ubuntu 18 , mpm_prefork vs mpm_event
- From: Tomasz Neugebauer <Tomasz.Neugebauer@concordia.ca>
- [EP-tech] Ubuntu 18 , mpm_prefork vs mpm_event
- References:
- [EP-tech] Ubuntu 18 , mpm_prefork vs mpm_event
- From: Tomasz Neugebauer <Tomasz.Neugebauer@concordia.ca>
- [EP-tech] Ubuntu 18 , mpm_prefork vs mpm_event
- Prev by Date: Re: [EP-tech] related_resources field display
- Next by Date: Re: [EP-tech] related_resources field display
- Previous by thread: [EP-tech] EPrints/CRIS
- Next by thread: [EP-tech] DOI handling in orcid_support_advance
- Index(es):