ius-coredev team mailing list archive

[kustodian <1312972@xxxxxxxxxxxxxxxxxx>]

Creating the apache user if it doesn't exists is an ok solution.

There is still a problem with setting the permissions of the /var/log
/php-fpm directory after each package upgrade which is done in the line
you mentioned:

%attr(770,apache,root) %dir %{_localstatedir}/log/php-fpm

Since root is writing into that directory, it's not a problem to remove
the %attr macro and just leave the default permissions (root:root 755).
If someone wants to tighten the permissions, they can change them
manually and they will stay like that. That is far better than to set
the new permissions each time the package is upgraded.

-- 
You received this bug notification because you are a member of IUS Core
Development, which is subscribed to IUS Community Project.
https://bugs.launchpad.net/bugs/1312972

Title:
  php54-fpm "warning: user apache does not exist - using root"

Status in IUS Community Project:
  In Progress

Bug description:
  If you install/upgrade php54-fpm and Apache is not installed (which is
  usually the case if you are using Nginx), the php54-fpm prints this
  warning:

  "warning: user apache does not exist - using root"

  What I noticed is that this sets the owner of /var/log/php-fpm
  directory to owner root and 770 mode:

  $ ls -ld /var/log/php-fpm/
  drwxrwx---. 2 root root 4096 Apr  4 15:58 /var/log/php-fpm/

  
  This is a problem because php-fpm cannot write anything into that directory because of this. And the biggest problem is that if you set permissions and owner to the user which runs php-fpm (which is nginx in my case) after the package is upgraded, it overwrites those permission again.

  This same thing happens with php55u-fpm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ius/+bug/1312972/+subscriptions