| 1 |
For example in crontab */3 means "every three hours/minutes/etc". |
| 2 |
|
| 3 |
2014-08-01 21:32 GMT+04:00 Alan McKinnon <alan.mckinnon@×××××.com>: |
| 4 |
> Hi, |
| 5 |
> |
| 6 |
> Up-front disclaimer: Mostly [OT] post. But at least I'll test drive it |
| 7 |
> on Gentoo before putting it in production :-) |
| 8 |
> |
| 9 |
> New job, new environment. Existing persons suffer from |
| 10 |
> 5-year-old-with-a-hammer syndrome and assume cron is the solution to all |
| 11 |
> ills. Result: a towering edifice of cron jobs that may or may not |
| 12 |
> clobber each other's work, may or may not work at all, and implement no |
| 13 |
> error handling at all. But my god, can they spew out mail from STOUT |
| 14 |
> |
| 15 |
> |
| 16 |
> But cron has only one event trigger: wall-clock time. And it's a very |
| 17 |
> blunt weapon. I'm looking for recommendations of alternative schedulers |
| 18 |
> that satisfy real-world business needs that need some other event |
| 19 |
> trigger than what the time is right now. |
| 20 |
> |
| 21 |
> For those familiar with it, I'm looking for something with the useful |
| 22 |
> feature set, without the useless features and without the price tag of |
| 23 |
> ControlM |
| 24 |
> |
| 25 |
> Anyone care to share experiences? |
| 26 |
> |
| 27 |
> |
| 28 |
> -- |
| 29 |
> Alan McKinnon |
| 30 |
> alan.mckinnon@×××××.com |
| 31 |
> |
| 32 |
> |
Archives