ius-coredev team mailing list archive

[Carl George <carl.george@xxxxxxxxxxxxx>]

>From what I can tell, the logging is all done by the master fpm process,
which runs as root.  I agree that the directory should not be owned by
the apache user, however I think it should be OK for the directory to be
owned by root.  As far as manual changes being overwritten, that is
because the SPEC file currently specifies the directory owner.

https://github.com/iuscommunity-
pkg/php54/blob/master/SPECS/php54.spec#L1396

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

Would it be acceptable to just remove the %attr macro?  The directory
would then default to (755,root,root), and future changes of ownership
would not be overwritten.

** Changed in: ius
       Status: New => In Progress

** Changed in: ius
     Assignee: (unassigned) => Carl George (carl.george)

-- 
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