RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
In the documentation for Procedure 4.1 it is stated:
 To configure the auditd and rsyslogd daemons to automatically start at boot, run the following commands as the root user:

    ~]# chkconfig --levels 2345 auditd on

    ~]# chkconfig --levels 2345 rsyslog on

    Use the systemctl status service-name.service command to check if these services are running, for example: 

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
Documentation should say:
 To configure the auditd and rsyslogd daemons to automatically start at boot, run the following commands as the root user
# systemctl is-enabled auditd
# systemctl is-enabled rsyslog

or run the following commands and serach for enabled in the Loaded (/usr/lib.../auditd.service;enabled) line
#systemctl status auditd
#systemctl status rsyslog



Additional info:

Documentation should say:
 To configure the auditd and rsyslogd daemons to automatically start at boot, run the following commands as the root user:
#systemctl enable auditd.service
#systemctl enable rsyslog.service


Use the systemctl status service-name.service command to check if these services are running, for example: 
# systemctl is-enabled auditd
# systemctl is-enabled rsyslog

or run the following commands and search for enabled in the Loaded line (/usr/lib.../auditd.service;enabled)
#systemctl status auditd | grep enabled
#systemctl status rsyslog | grep enabled