Bug 1231924

Summary: outdated documentation of 'apachectl status'
Product: Red Hat Enterprise Linux 7 Reporter: Martin Frodl <mfrodl>
Component: httpdAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: Martin Frodl <mfrodl>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: jkaluza, jorton
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: httpd-2.4.6-35.el7 Doc Type: Bug Fix
Doc Text:
Cause: Man page for "apachectl status" was not updated after the migration to systemd. Consequence: Man page for "apachectl status" mentioned old way how the "apachectl status" worked in RHEL-6. Fix: Man page has been updated to reflect the systemd migration. Result: Man page for "apachectl status" is now correct.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 04:38:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Frodl 2015-06-15 15:50:28 UTC
Description of problem:

The behaviour of 'apachectl status' changed between RHEL 6 and 7. In RHEL 6, it is basically a flavour of 'apachectl fullstatus', i.e. it returns a server status page generated by mod_status. In RHEL 7, by contrast, 'apachectl status' is a mere synonym to 'systemctl status httpd'. Two very different beasts, yet the documentation is same for both, cf. 'man apachectl' on RHEL 6 and 7:

...
       status Displays a brief status report. Similar to the fullstatus
              option, except that the list of requests currently  being
              served is omitted.
...

Provided the functionality is not going to change, the RHEL-7 apachectl man page should be updated to reflect the actual behaviour.

Version-Release number of selected component (if applicable):
httpd-2.4.6-31.el7.x86_64

Comment 6 errata-xmlrpc 2015-11-19 04:38:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2194.html