From: LeamHall <LeamHall@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package php-fpm tries to use user and group http
Date: Fri, 11 Jun 2021 15:42:06 +0200 [thread overview]
Message-ID: <20210611134206.fnZIjyCiFpujYLhpt2oNpkYWhGtbYx4YUtyybwvGkzs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31422@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
New comment by LeamHall on void-packages repository
https://github.com/void-linux/void-packages/issues/31422#issuecomment-859591003
Comment:
I am not a web person nor have I ever built my own Linux distro. My ideas are just ideas, I'm not sure if they are any good.
What permissions does php-fpm need? Does it need write access to the web directories? Does it need the UID/GID of whatever is serving httpd?
Changing Apache at this point would be a bit of work, and established servers might have an issue. I'm not sure how many sites are using the php-fpm package, but it might be fewer than are using Apache or Nginx.
If php-fpm just needs read access to the web files, then it could just test for read file/execute directory access on the installed package's ServerRoot. The php-fpm package could then use whatever UID/GID it wanted, and create. If it must use an httpd server's UID/GID, then it may need to search for whatever is installed, and default to http.
next prev parent reply other threads:[~2021-06-11 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 2:36 [ISSUE] " LeamHall
2021-06-11 5:16 ` ericonr
2021-06-11 13:42 ` LeamHall [this message]
2021-06-17 17:58 ` the-eater
2021-06-17 19:00 ` LeamHall
2022-05-22 2:11 ` github-actions
2022-06-05 2:13 ` [ISSUE] [CLOSED] " github-actions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210611134206.fnZIjyCiFpujYLhpt2oNpkYWhGtbYx4YUtyybwvGkzs@z \
--to=leamhall@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).