Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 14862 - run-crons has 'month' time set to 30 days, instead of 31.
Summary: run-crons has 'month' time set to 30 days, instead of 31.
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: Preston A. Elder (RETIRED)
URL:
Whiteboard:
Keywords:
: 14961 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-01-31 12:10 UTC by Preston A. Elder (RETIRED)
Modified: 2003-03-16 14:00 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Preston A. Elder (RETIRED) gentoo-dev 2003-01-31 12:10:42 UTC
User-Agent:       
Build Identifier: 

The run-crons script will check to see if the monthly events have been run in
the last 30 days (30 days and 5 minutes), and will run them if they have not. 
This should actually be 31 days.  The 'cron.monthly' file will be removed on the
first of the month, to ensure that events are run then anyway, and setting this
to 30 days means that on months with 31 days in them, monthly events will occur
on the 1st of the month, on the 30th of the month, and again the 1st of the next
month.

Setting the amount of time between monthly events to 31 days will fix this
problem, since on months with less than 31 days, the removal of the cron.monthly
file on the 1st of the month will ensure they happen on the first of the month
anyway.

Reproducible: Always
Steps to Reproduce:
Just have a monthly event active, and wait for a 31-day month to come around :)
Comment 1 Preston A. Elder (RETIRED) gentoo-dev 2003-01-31 13:38:26 UTC
Changed month time from 30 -> 31 days.
Comment 2 Robert Coie (RETIRED) gentoo-dev 2003-03-16 14:00:32 UTC
*** Bug 14961 has been marked as a duplicate of this bug. ***