Bug 1292395 - Obsolete RHEL 6 SELinux guide reference in the rsyslog logging server section
Obsolete RHEL 6 SELinux guide reference in the rsyslog logging server section
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-System_Administrators_Guide (Show other bugs)
7.0
Unspecified Unspecified
high Severity unspecified
: rc
: ---
Assigned To: Maxim Svistunov
ecs-bugs
: Documentation
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-17 05:21 EST by Armando Vega
Modified: 2016-11-14 11:51 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-14 11:51:03 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Armando Vega 2015-12-17 05:21:04 EST
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/s1-configuring_rsyslog_on_a_logging_server.html

Section Number and Name: 20.5 Configuring rsyslog on a Logging Server

Describe the issue: Towards the end of the first subsection there is a reference to the SELinux guide for RHEL 6. Even though it might still be relevant, it would probably be better to direct users to the new guide with more current information on the subject.

Suggestions for improvement: Change the reference to point to the RHEL 7 version of the SELinux guide that can be found on https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SELinux_Users_and_Administrators_Guide/index.html

Additional information: None
Comment 2 Jana Heves 2015-12-17 14:16:40 EST
Hello Armando,

Thank you very much for taking your time to file this bug.
I've changed the link and title as follows:

For more information on SELinux, see Red Hat Enterprise Linux 7 SELinux User's and Administrator's Guide. 

This change will appear on the Customer Portal by the end of this calendar year. 
Thanks,
jana

Note You need to log in before you can comment on or make changes to this bug.