Bug 505309
Summary: | cron is off its chum again | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tom Horsley <horsley1953> | ||||
Component: | anacron | Assignee: | Marcela Mašláňová <mmaslano> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 11 | CC: | mmaslano, pertusus, tmraz | ||||
Target Milestone: | --- | Keywords: | Reopened | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-06-18 12:06: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: | |||||||
Attachments: |
|
Description
Tom Horsley
2009-06-11 12:58:12 UTC
Created attachment 347395 [details]
cron log
I might as well attach the whole cron log, it hasn't gotten very big yet.
Hello, makewhatis is at first run by cron.daily and then by cron.weekly. This is strange behaviour of makewhatis, which will be changed in new version. You can't blame cron for this issue. Best regards, Marcela What about the two cron.weekly runs in two days? Ok, that's a problem. It works for me. Does it make a time stamp in /var/spool/anacron/cron.weekly ? Does cron.weekly run every day on your machine? I won't know if it runs every day till tomorrow :-). Perhaps I rebooted it yesterday before weekly got finished and it therefore decided it needed to start from scratch again? Things like this are why I always disable the anacron service, but now I see it isn't a separate service, which is why I wondered if I could erase the anacron package in order to disable the "helpful" anacron behavior? Here's the timestamp I have today: [root@tomh ~]# ls -l /var/spool/anacron/cron.weekly -rw------- 1 root root 9 Jun 11 08:49 /var/spool/anacron/cron.weekly [root@tomh ~]# cat /var/spool/anacron/cron.weekly 20090611 (In reply to comment #5) > I won't know if it runs every day till tomorrow :-). > > Perhaps I rebooted it yesterday before weekly got finished and it > therefore decided it needed to start from scratch again? Yes, that could be only reason. If the job didn't finish and created time stamp, then it'll start again. |