Bug 428899

Summary:	/etc/sysconfig/selinux should be a relative symlink
Product:	Red Hat Enterprise Linux 4	Reporter:	Jeff Bastian <jbastian>
Component:	selinux-policy-targeted	Assignee:	Daniel Walsh <dwalsh>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.6	CC:	dwalsh
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-08-01 14:31:12 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:

Description Jeff Bastian 2008-01-15 22:24:06 UTC

+++ This bug was initially created as a clone of Bug #181752 +++

Description of problem:
/etc/sysconfig/selinux is created as a symlink to /etc/selinux/config.

sysreport/sosreport captures this absolute symlink and can confuse the person
looking at the report (me!) when the sestatus output doesn't match
/etc/sysconfig/selinux

I'll try to get into the habit of looking at /etc/selinux/config instead, but as
long as the symlink is there, it should be a relative symlink.

This has been fixed in newer versions of the policy.  Please backport it to RHEL
4.7.

Version-Release number of selected component (if applicable):
RHEL 4.6 selinux-policy-targeted-1.17.30-2.149

Comment 1 Daniel Walsh 2008-08-01 14:31:12 UTC

Not worth the backport.  We do not intend to update RHEL4 policy.