Bug 33422 – rhnsd runs unnecessarily

Bug 33422 - rhnsd runs unnecessarily

Summary:	rhnsd runs unnecessarily

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	up2date (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Preston Brown
QA Contact:	Jay Turner
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-03-27 12:01 EST by Matthew Kirkwood
Modified:	2015-01-07 18:44 EST (History)
CC List:	3 users (show)

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

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Matthew Kirkwood 2001-03-27 12:01:31 EST

The default install of up2date runs rhnsd unconditionally.  Given that some
people have privacy worries about the disappearance of non-anon up2date, it
would be wise to change this.

Since the RHN registratration process runs as root, it should suffice to
"chkconfig rhnsd on" (and maybe "service rhnsd start") when first
configured.

This would have saved the 7.0 fd leak embarrasment too, since signups would
have got the update before rhnsd had had a chance to run for too long.

Comment 1 Preston Brown 2001-03-27 12:54:12 EST

We agree.  rhnsd's init script will check for the existence of 
/etc/sysconfig/rhn/systemid before starting, and rhn_register will attempt to 
start rhnsd if it is not already running after successful registration.

Comment 2 Daniel Roesen 2001-03-27 13:39:18 EST

Heh, how opinions can change... :->

See Bug #17934

Comment 3 Preston Brown 2001-03-28 13:40:28 EST

yes, opinions can change.

Changed in rawhide (2.4.6 and later).

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