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 103381

Summary:	chkconfig reports an error and stops running when broken symlink in /etc/init.d present
Product:	[Retired] Red Hat Linux	Reporter:	Brian Zammit <bzammit>
Component:	chkconfig	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DUPLICATE	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9	CC:	rvokal
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:	2006-02-21 18:58:20 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 Brian Zammit 2003-08-29 15:21:51 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Win 9x 4.90)

Description of problem:
See summary. Also, the exact message shown is:

error reading from directory /etc/init.d: No such file or directory

At this point, processing of /etc/init.d/ stops. chkconfig should handle the 
broken symlinks better then this.

Similar to bug 74324 based on RH7.3, but it still hasn't been fixed in 9.

Version-Release number of selected component (if applicable):
chkconfig-1.3.8-1

How reproducible:
Always

Steps to Reproduce:
1. have a broken symlink in /etc/init.d/
2. run chkconfig --all
3. watch chkconfig fail on the broken symlink with the above error message
    

Actual Results:  chkconfig stopped processing /etc/init.d

Expected Results:  chkconfig should process the /etc/init.d directory 
completely.

Additional info:

Comment 1 Bill Nottingham 2005-02-02 21:01:40 UTC


*** This bug has been marked as a duplicate of 74324 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:58:20 UTC

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.