Bug 665176

Summary: There is no selinux man page for mysql
Product: Red Hat Enterprise Linux 6 Reporter: Yogesh Babar <ybabar>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: low Docs Contact:
Priority: low    
Version: 6.0CC: dwalsh, mgrepl, mhideo, mmalik
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: selinux-policy-3.7.19-107.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 09:46:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 645519    
Attachments:
Description Flags
MySQL man page
none
How about. none

Description Yogesh Babar 2010-12-23 01:05:40 UTC
Description of problem:
I have found that for every major service in RHEL there is a corresponding <service>_selinux man page but there is no such man page for mysql and selinux contexts are not documented anywhere.  

Version-Release number of selected component (if applicable):
man-pages-3.22-12.el6.noarch

How reproducible:
Always

Steps to Reproduce:
n/a

Actual results:
No selinux man page for mysql

Expected results:
There should be a mysql_selinux man page

Additional info:

Comment 3 Miroslav Grepl 2011-06-14 13:59:54 UTC
Patches accepted ;-)

... I want to write man pages also for other daemons.

Comment 4 Miroslav Grepl 2011-08-08 10:42:11 UTC
Created attachment 517163 [details]
MySQL man page

I suggest this man page.

Comment 5 Daniel Walsh 2011-08-08 14:36:50 UTC
Created attachment 517235 [details]
How about.

Comment 6 Miroslav Grepl 2011-08-08 14:55:30 UTC
Good idea to add FILE_CONTEXTS and PORTS sections.

Comment 7 Miroslav Grepl 2011-08-10 15:17:41 UTC
Fixed in selinux-policy-3.7.19-107.el6

Comment 10 errata-xmlrpc 2011-12-06 09:46: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.

http://rhn.redhat.com/errata/RHBA-2011-1511.html