htscanner suddenly enabled

I am running custombuild 2.0, and I run mod_php with mod_ruid2. Few days ago, suddenly I find this in settings when doing ./build options:


Then I check the content of /usr/local/directadmin/custombuild/options.conf and I see that htscanner is set to yes without me doing it:


What impact will this have on my server? Why was it added and set to YES without any announcement first? When I read about htscanner after doing a Google search, it seems to me it is not something you would want to install when running PHP as mod_php with mod_ruid2 - I think it is only for those that run PHP in cgi mode (suphp etc). I found this: http://pecl.php.net/package/htscanner

Allow one to use htaccess-like file to configure PHP
per directory, just like apache's htaccess. It is especially useful with fastcgi (ISS5/6/7, lighttpd, etc.).
This package was originally developed by Bart Vanbrabant. Old versions are available
from: http://files.zoeloelip.be/htscanner

Click to expand...

Now I am afraid that the next time I recompile PHP, that htscanner will automatically be compiled, and then I am afraid if that is going to create problems. I don't like surprises. Please, smtalk, or John, explain this, please answer if I should set htscanner to NO in options.conf when I am only running PHP as mod_php with mod_ruid2?

Thank you for the question Please check http://forum.directadmin.com/showthread.php?t=25115&p=241638#post241638. It is not enabled (even if it's set to "yes"), if php mode is mod_php.

Thank you for the information! Then I will set htscanner to "no" in options.conf. I understand you say it is not enabled when I run mod_php, but I still think I like to change it to "no". Thanks.

I run mod_php but nevertheless it is enabled in httpd-phpmodules.conf as soon as i do a ./build rewrite_confs.
When htscanner=no the httpd-phpmopdules.confm is generated correct.

Do you have a 2nd version of PHP selected?

I too had to set htscanner=no and do a rewrite configs..