Hi,
On Thu, Oct 27, 2016 at 4:57 PM, Gordon Messmer
<gordon.messmer(a)gmail.com> wrote:
On 10/27/2016 01:44 PM, Alex wrote:
>
> I've actually already done these exact steps, and it doesn't work (on
> fedora23). When you say you've tested it, do you mean you tested the
> steps above, or you did something to confirm afterwards that its umask
> is 0002?
I created a php script that created a new file. Before the change, the
file's mode was 0644. After the change, the mode was 0664.
You previously said that you'd tried to override the umask by editing
/etc/systemd/system/multi-user.target.wants/httpd.service, which is not the
same file.
Follow the steps I offered, exactly.
> # cat /etc/systemd/system/httpd.service.d/override.conf
> [Service]
> UMask=0002
> # systemctl restart httpd
> # su - apache -s /bin/bash
> -bash-4.3$ umask
> 0022
The process I documented doesn't change the umask for the user,
only for the httpd process started by systemd.
Ah yes, of course, thanks. This UMask change has been in place for
more than a week, and the joomla developers have still been
complaining about write problems, but I'll test manually with joomla
again. Specifically, uploading new modules have been created with 0644
and 0755.