Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 74324

Summary:	chkconfig stops if symlink cannot be resolved in /etc/init.d
Product:	[Retired] Red Hat Linux	Reporter:	Peter Bieringer <pb>
Component:	chkconfig	Assignee:	Bill Nottingham <notting>
Status:	CLOSED RAWHIDE	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	bzammit, jik, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	1.3.14-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-02-02 20:57:01 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 Peter Bieringer 2002-09-20 13:57:46 UTC

Description of problem:
if /etc/init.d contains an unresolvable symlink to an external program,
chkconfig will stop immediately

Version-Release number of selected component (if applicable):
chkconfig version 1.3.5

How reproducible:
Always

Steps to Reproduce:
1. # ln -sf /tmp/notexist /etc/init.d/notexist
2. # chkconfig --list
keytable        0:off   1:on    2:on    3:on    4:on    5:on    6:off
...
syslog-ng       0:off   1:off   2:on    3:on    4:on    5:on    6:off
error reading from directory /etc/init.d: No such file or directory[root@gromit
init.d]#
	

Actual Results:  Not displaying anymore information

Expected Results:  Fulfilling list, perhaps displaying a message about such symlink

Additional info:

Comment 1 Bill Nottingham 2005-02-02 20:57:01 UTC

fixed in 1.3.14-1.

Comment 2 Bill Nottingham 2005-02-02 21:02:22 UTC

*** Bug 103381 has been marked as a duplicate of this bug. ***

Comment 3 Bill Nottingham 2005-02-02 21:21:49 UTC

*** Bug 107838 has been marked as a duplicate of this bug. ***