Bug 3002 – inetd set to start at the wrong runlevel

Bug 3002 - inetd set to start at the wrong runlevel

Summary:	inetd set to start at the wrong runlevel

Status:	CLOSED CURRENTRELEASE

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-05-24 09:39 EDT by bigboss
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-05-24 10:40:00 EDT
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 bigboss 1999-05-24 09:39:18 EDT

I installed 2 machines with Redhat 6.0 and enabled inetd
durring the install. Both of the installs enabled it at
runlevel 4, which is unused in RH6. Using chkconfig I added
it to runlevel 3 and all works as expected now.

Comment 1 Derek Tattersall 1999-05-24 10:40:59 EDT

Selecting inet on the services to start menu of the install causes
inet to be a start service in levels 3, 4, 5.  It is a kill service in
level 0, 1, 2, 6.  Can't duplicate your experience.

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