Red Hat Bugzilla – Bug 137365
Upgrading packages with services re-enabled/re-installed in /etc/rc.d/rc?.d
Last modified: 2007-11-30 17:10:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
Upgrading packages through rpm or upgrade encapsulated with yum has
the nasty side-effect that services are re-enabled/re-installed to
The recent update of package cups (cups-1.1.20-11.6 from 25-Oct-2004)
shows this behaviour. I have default killed most services after
install using chkconfig --del <service>. Services are only enabled
when needed. Upgrading cups to the new packages reinstalled the
init-script links in /etc/rc.d/rc.d, resulting that the package
would autostart at next reboot.
This is a security issue because services are generally disabled for a
reason and should remain disabled until the sys-admin decides otherwise.
Second reason why this behaviour is unwanted, is that some services
are "heavy" to start and you just don't want them arround all the time.
Third reason is that systems under remote administration can be setup
with automatic update (think of home users where the sysadmin is far
away). You want to keep the system up-to-date but do not want the
default configuration to change.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install cups from distro CD
2. remove service: # chkconfig --del cups
3. upgrade: # yum update cups
Actual Results: Cups autostarts again in runlevel 2, 3, 4, and 5.
Expected Results: No autostart.
Other packages are also involved, like privoxy. From the view of it,
all packages reinstall themselfs in /etc/rc.d/rc?.d when they default
to it in the install phase (i.e. the links are included in the spec-file).
The correct way to disable is with:
chkconfig --level <levels> <service> off
chkconfig --del <service>