RHEL9 - apachectl script doesn't support expected params

[jesusbagpuss]

Based on RHEL9.8:

> which apachctl
/sbin/apachectl

> apachectl -S
apachectl: The "-S" option is not supported.

In the /sbin/apachectl file, there is this message:

### NOTE: This is a replacement version of the "apachectl" script with
### some differences in behaviour to the version distributed with
### Apache httpd.  Please read the apachectl(8) man page for more
### information.

The get_process_name function does identify the correct httpd, but preflight check 3.1 happens before the process name is considered, causing e.g. checks 16.2 to fail.

Side note:
On my RHEL9 server there are two identical copies (not symlinks) of httpd:

• /sbin/httpd
• /usr/sbin/httpd

I am unsure why there are two. The apachectl wrapper references /usr/sbin/httpd, and this is what the httpd.service runs.
The version returned by which httpd is the /sbin/httpd version.!?

[richardforth]

I've not been able to support RHEL properly since RHEL7 when I had access to servers at work.

It sounds like something has changed on the RHEL 9 builds that I no longer can see.

If you put a pull request in from staging, I can run it through the Jenkins pipeline for the docker containers I have and check it doesn't break anything and I'll approve

[jesusbagpuss]

Hi @richardforth , I'll submit a PR covering all three of the Issues I've just submitted. The main aspect with this one is what would be preferable to use in the pre-flight checks - we can discuss after I've made a PR :)

[richardforth]

Yep it could get messy, the preflight checks generally dictate which executables are used later on in the script execution but it's been a while since I worked on this project so I'm a bit rusty.

If you can test on RHEL9 and you're happy with it, I can try and fire up the Jenkins environment (it probably needs an update) and run the pipelines to check nothing backwards is breaking for the other OSes.