emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#45937: closed ([PATCH] gnu: php-fpm: Ensure no duplicate group.)


From: GNU bug Tracking System
Subject: bug#45937: closed ([PATCH] gnu: php-fpm: Ensure no duplicate group.)
Date: Sun, 17 Jan 2021 19:47:02 +0000

Your message dated Sun, 17 Jan 2021 20:45:58 +0100
with message-id 
<ef383c8cc40c511d7f3f51fc72176c65d0e5b9e1.camel@student.tugraz.at>
and subject line Re: [PATCH] gnu: php-fpm: Ensure no duplicate group.
has caused the debbugs.gnu.org bug report #45937,
regarding [PATCH] gnu: php-fpm: Ensure no duplicate group.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
45937: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=45937
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH] gnu: php-fpm: Ensure no duplicate group. Date: Sun, 17 Jan 2021 17:00:00 +0100
Hi Guix!

When updating my system, I noticed there was a duplicate php-fpm group.
The reason is that by default, the group is php-fpm, and the accounts
list contains php-fpm and the configured group. I'm not sure why, but
the hardcoded php-fpm group seems to be used by the user as a
supplementary group.

This patch only adds the php-fpm group when the configured group is not
already php-fpm. If you think it'd be better, we could also simply
remove the hard-coded php-fpm group and the supplementary group from
the php-fpm user.

Attachment: 0001-gnu-php-fpm-Ensure-no-duplicate-group.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: [PATCH] gnu: php-fpm: Ensure no duplicate group. Date: Sun, 17 Jan 2021 20:45:58 +0100 User-agent: Evolution 3.34.2
Hi Julien,

I've pushed your patch with a small indentation fix.

Am Sonntag, den 17.01.2021, 17:00 +0100 schrieb Julien Lepiller:
> This patch only adds the php-fpm group when the configured group is
> not
> already php-fpm. If you think it'd be better, we could also simply
> remove the hard-coded php-fpm group and the supplementary group from
> the php-fpm user.
I'm not quite sure, but I think the use case here would be having a
www-admin group with full access to the entire directory structure and
some local users, who only have access to some directories as members
of the php-fpm group.  I might be wrong on that though, php-fpm users
please correct me if I am.

Regards,
Leo



--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]