how to register cwp-httpd in the os/system as default httpd Apparently cwp-httpd is not registered os/systemwide as httpd. For some reason CWP also installed httpd 2.4.6 (/etc/httpd) which just sits dormant. Any CLI interaction thus is not with cwp-httpd but the dormant httpd instead, e.g.
httpd -t -D DUMP_RUN_CFG
results in
ServerRoot: "/etc/httpd"
Main DocumentRoot: "/var/www/html"
Main ErrorLog: "/etc/httpd/logs/error_log"
Mutex default: dir="/run/httpd/" mechanism=default
Mutex mpm-accept: using_defaults
Mutex authdigest-opaque: using_defaults
Mutex proxy-balancer-shm: using_defaults
Mutex rewrite-map: using_defaults
Mutex authdigest-client: using_defaults
Mutex proxy: using_defaults
Mutex authn-socache: using_defaults
PidFile: "/run/httpd/httpd.pid"
Define: _RH_HAS_HTTPPROTOCOLOPTIONS
Define: DUMP_RUN_CFG
User: name="apache" id=48
Group: name="apache" id=48
vs. /usr/local/apache/bin/httpd -t -D DUMP_RUN_CFG
ServerRoot: "/usr/local/apache"
Main DocumentRoot: "/home"
Main ErrorLog: "/usr/local/apache/logs/error_log"
Mutex default: dir="/usr/local/apache/logs/" mechanism=default
Mutex rewrite-map: using_defaults
Mutex ssl-stapling-refresh: using_defaults
Mutex ssl-stapling: using_defaults
Mutex proxy: using_defaults
Mutex ssl-cache: using_defaults
PidFile: "/usr/local/apache/logs/httpd.pid"
Define: DUMP_RUN_CFG
User: name="nobody" id=99
Group: name="nobody" id=99
Again, this is lacking transparency and is not documented in the wiki. It may also incur lot of confusion, not only for the user but also applications depending on httpd.
In the above described setup provided by CWP no other application is recognising cwp-httpd as httpd only when manually pointed to by (CWP) scripts.
Whilst the dormant httpd 2.4.6 can be safely removed (yum remove httpd) I would like to know
how to register cwp-httpd in the os/system as default httpd for other application to recognise (and the user to be able to interact via CLI with the direct httpd command).