Bug 137365
| Summary: | Upgrading packages with services re-enabled/re-installed in /etc/rc.d/rc?.d | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bertho <bertho> |
| Component: | rpm | Assignee: | Jeff Johnson <jbj> |
| Status: | CLOSED NOTABUG | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2 | CC: | nobody+pnasrat |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-10-27 20:02:46 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: | |||
The correct way to disable is with: chkconfig --level <levels> <service> off Not with: chkconfig --del <service> |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922 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 autostart. 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[2345].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): How reproducible: Always 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. Additional info: 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).