On Mon, Jan 11, 2010 at 8:06 AM, Paul Mattal <paul@mattal.com> wrote:
On 01/06/2010 01:09 AM, Paul Mattal wrote:
Proposal: We stay with dcron into the 4.0 series, with a longer-than-usual testing window so the transition is smooth, and see if it meets our collective needs. Jim may be willing to add functionality we find lacking.
Please get your votes and comments in by the weekend, if possible. I'd like to move on this next week, if we have agreement.
I've just placed dcron 4.2 into [testing]. This is a major update to dcron, under a new maintainer (who is an Arch user, and very responsive). With this release, I am also taking over maintaining dcron in [core].
I'd like to get 2 signoffs for each architecture for this one, since it represents a lot of new functionality. Full changelist since 3.2 inlined below. For further info, and a full git history, see:
http://www.jimpryor.net/linux/dcron
- P
***
Why did you put etc/rc.d/crond in the backup array? These daemon scripts are not intended to be modified by the user. If you want them to be able to pass different options, you should use a /etc/conf.d/crond config file. Eric