All, Devs, Why do we have the package system-user-wwwrun? Yes it creates the user/group for the webserver to run as, but it totally conflicts with the nginx webserver default nginx:nginx, and there is no requirement that a webserver run as www:wwwrun -- none at all. The downside to this type "nanny" package is it creates confusion on updates suggesting that php must be completely uninstalled if the package system-user-wwwrun or requiring the user to choose "break" php by ignoring some of its dependencies. Running php-fpm under user/group www:wwwrun is NOT a valid php dependency - period. After installing nginx, I configured the web server to run as nginx:nginx based on the default installed nginx user/group. It already creates the nginx user/group, so there is no reason for the system-user-wwwrun dependency on php trying to change that. Now every time I try and update Tumbleweed it tries to uninstall php and I'm forced to choose the false option to "break" php every update. These nanny packages should be optional and NOT a dependency. They can be "Recommended", but dependencies are supposed to be real dependencies not some made up user-preference masquerading as a dependency. Php-fpm does not care what user it runs as. That is a simple 2 line config issue: user = nginx group = nginx So why do we have system-user-wwwrun as a hard php dependency, and why is the user not capable of following the wealth of examples and tutorials out there to set up the server? It just seems this is a totally unnecessary package that causes more problems than it purportedly solves. It creates a circular-dependency hell that shouldn't exist in the first place and screws up updates. -- David C. Rankin, J.D.,P.E.