Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 3002

Summary: inetd set to start at the wrong runlevel
Product: [Retired] Red Hat Linux Reporter: bigboss
Component: installerAssignee: David Lawrence <dkl>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-05-24 14:40:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description bigboss 1999-05-24 13:39:18 UTC
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 14:40:59 UTC
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.