Bug 1190259

Summary:	Section 4.1.8.2.3. rhnsd needs an update to cover enabling for RHEL7
Product:	Red Hat Satellite 5	Reporter:	Michael J. Ayers <ayersmj>
Component:	Docs Client Config Guide	Assignee:	Dan Macpherson <dmacpher>
Status:	CLOSED NOTABUG	QA Contact:	Dan Macpherson <dmacpher>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	570	CC:	ayersmj, xdmoon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-03 17:43: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:
Bug Depends On:
Bug Blocks:	1127217

Description Michael J. Ayers 2015-02-06 19:51:50 UTC

Description of problem:
Section 4.1.8.2.3 needs a Note section on how to enable rhnsd in RHEL7.x.


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


How reproducible:
N/A

Steps to Reproduce:
N/A

Actual results:
N/A

Expected results:
N/A

Additional info:
The commands enabling rhnsd for RHEL7 to be added to a Note appending section 4.1.8.2.3:

systemctl enable rhnsd
systemctl start rhnsd

Comment 2 Dan Macpherson 2015-02-17 01:46:05 UTC

Hi Michael,

This bug shouldn't apply because that section only applies to UNIX/Solaris clients, not RHEL clients.

Section 4.1.8.2.3 states:

"On Red Hat Enterprise Linux systems, the rhnsd daemon, which instructs the client system to check in with Red Hat Network, automatically starts at boot time. On Solaris systems, rhnsd does not start at boot time by default."

I couldn't find any non-Solaris references to rhnsd in this book.

Michael, just to check though, are there any other updates in the Client Configuration Guide needed for this bug? Or is it okay to close it?

Comment 3 Michael J. Ayers 2015-03-03 15:20:31 UTC

Go ahead and close.

Comment 4 Dan Macpherson 2015-03-03 17:43:07 UTC

Thanks, Michael! Closing the bug.