Bug 13625
| Summary: | anacron "FAILED" on shutdown | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Gene Czarcinski <gczarcinski> |
| Component: | anacron | Assignee: | Bernhard Rosenkraenzer <bero> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | ||
| 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: | 2000-07-09 19:30:25 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
Gene Czarcinski
2000-07-09 16:04:58 UTC
Considering anacron isn't a daemon and unless it is working on something that is taking a long time normally wouldn't be running during shutdown, it doesnt seem appropriate to show a [ FAILED ] notice for stopping anacron. Might as well leave it alone and let it get hit with all the other process as a TERM/KILL is sent. Is it even a good idea to have anacron run at that point in the startup anyway? A script placed in /etc/cron.* might require another service that isn't running, such as a database server, a web server, a news server, etc. Currently anacron is being started even before networking is up... Fixed in 2.3-5. It's treated like a daemon because we want it to be run at runlevel changes (cron is not necessarily running in runlevel 1); someone messed up the ifs while moving over to the new start() scheme. |