0

Each time I update php-fpm on my server it installs a new www.conf file that interferes with my existing configuration. Is there any way to block it from being overwritten each time?

1
  • 1
    As a side note, one may want to version control important configuration files, e.g., cd /etc/ ; sudo git init ; sudo git add . ; sudo git commit -m 'initial'
    – cjc
    Jun 20, 2014 at 1:14

1 Answer 1

2

rpm should be creating a new www.conf called www.conf.rpmsave or www.conf.rpmnew if the www.conf already exists, it shouldn't be overwriting it.

If your configuration doesn't have a www.conf, the easy solution would be to just touch www.conf to make a new, blank one. If you ARE using www.conf and it is still overwriting it, then you're probably going to have to get heavy-handed with it.

chattr +i /etc/php-fpm.d/www.conf

Should do the trick. This will prevent anything anywhere from overwriting the file again. Next time you need to make a change to it, you'll have to use chattr -i on it, make your changes, then use chattr +i to reprotect it. These commands will have to be performed with root privileges (no surprise).

1
  • Thanks, though my real question is why there isn't a pools-available and pools-enabled…
    – mcdado
    Aug 10, 2017 at 19:01

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .