Sorry for the delay. We've had our hands full with the RHEL 7 and CentOS 7 releases.
The best solution I can come up with is to change the ownership to apache:apache, and then you can add users to the apache group to grant access. That will maintain the security of 770 permissions, without the headache of determining what user should own the directory, or changing the defaults Red Hat sets for the log directory. It will keep us very close to the Red Hat settings settings while still allowing us to accommodate your use case. Does this sound like a reasonable solution to you? -- 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 _______________________________________________ Mailing list: https://launchpad.net/~ius-coredev Post to : [email protected] Unsubscribe : https://launchpad.net/~ius-coredev More help : https://help.launchpad.net/ListHelp
