Bug 429850
| Summary: | crontab error with @reboot entry | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | jddceo <34supportserver> |
| Component: | vixie-cron | Assignee: | Marcela Mašláňová <mmaslano> |
| Status: | CLOSED ERRATA | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.6 | CC: | love03music05 |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-02-04 12:17:27 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 476972, 554606 | ||
|
Description
jddceo
2008-01-23 14:06:25 UTC
Well, there are two possibilities how to use @reboot macro. In our cron is reboot for start the job after reboot of computer, not after restart of the daemon. For the feature is needed new macro f.e. @restart. Please open an issue tracker for fix in RHEL-3|4. I'll be working on this feature in upstream. Sorry, but you are wrong, @reboot is the same like @restart, I only have @reboot in my crontab and they are executed each time I restart the daemon. Kind regards Alexander Ok, from your first comment wasn't clear what's the behavior now. Correct component is vixie-cron. yes, it is. I don't know if there is another one? I don't know how to understand your message. I changed bug on correct component. It was reported on crontabs, which is false. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0025.html |