[BUG] httpd-phpmodules.conf gets deleted as soon as build php is launched

[interfasys]

[BUG] httpd-phpmodules.conf gets wiped clean as soon as "build php" is launched

Before running build
# ls /etc/httpd/conf/extra
...
-rw-r--r--  1 root  wheel   230B Dec 23 00:06 httpd-phpmodules.conf
...

Now let's build php and interrupt it right after configure is done

# ./build php n
ctrl+c
# ls /etc/httpd/conf/extra
...
-rw-r--r--  1 root  wheel   0B Dec 23 00:08 httpd-phpmodules.conf
...

httpd-phpmodules.conf has been wiped clean

I'm sure it gets populated at the end of the build, but if the admin never completes the task, then httpd will never start during a routine restart

 

[smtalk]

Thank you for the report, but why do you think it is a bug? What if you interrupt the process in the middle of rewriting, would you consider it a bug too? We could make the rewrite of configuration files to be done later, but that would still be a problem if you interrupt it in the middle of the process. For the described case "./build rewrite_confs" would fix the problem.

 

[interfasys]

Thank you for the report, but why do you think it is a bug?

Because there is absolutely no reason to touch that file unless you've successfully compiled a new binary or generated a new config?

There are many reasons why a "build php" could fail and if the admin is not careful, he'll end up with an Apache config which won't start.
And you're right "./build rewrite_confs" would fix this, but it doesn't seem logical to me to fix my configs when I haven't updated anything on my system.

 

[Arieh]

I've had some trouble with this as well I think. Especially if you rebuild php on a live server and you have 2 php versions, so it takes a while to get both done. During the compiling processes httpd might get restarted by DA, and then it simply goes offline because the config file is messed up.

You can't do a rewrite confs in the meantime because it says another instance of CB is running.