Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removing last usage of a php fpm pool doesn't cleanly remove php #2

Open
mattheath opened this issue Feb 28, 2013 · 0 comments
Open
Labels

Comments

@mattheath
Copy link
Owner

Due to the config file purging, removing the last instance of a php fpm pool for a given version of php, which does not have that version required elsewhere, removes all of the php versions config. This causes the php version to no longer be configured, and the fpm service for that version to fail on start.

The behaviour is partly correct - the version of php should be removed if it's no longer required; however this should be done cleanly by shutting down the service and removing the php install.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant