Bug 160431 - "yum remove" can not clear /etc/dhclient-exit-hooks script
"yum remove" can not clear /etc/dhclient-exit-hooks script
Product: Fedora
Classification: Fedora
Component: firestarter (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael A. Peters
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2005-06-14 23:29 EDT by Yusuf Ma
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-30 17:33:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Yusuf Ma 2005-06-14 23:29:29 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; zh-CN; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
The message "... /etc/firestarter/firestarter.sh was not found" is displayed during determining the IP address from DHCP server when the system is booting up after the firestarter package was removed. I did not use graphical boot. I believe this message will not display in graphical boot.

This problem was traced to the fact that /etc/dhclient-exit-hooks file was not cleared after the package was removed. After removing "firestarter" line from this file, the problem is solved.

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

How reproducible:

Steps to Reproduce:
1. Install Firestarter package. Run firestarter and configure it.
2. Remove Firestarter package.
3. Restart the system.

Actual Results:  firestarter.sh not found message was displayed during booting process when DHCP is determining the IP address.

Expected Results:  status "OK" without any error message

Additional info:
Comment 1 Michael A. Peters 2006-01-30 17:33:40 EST
It should be fixed now in rawhide - a new release for fc4 will be pushed soon.

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