Other options include TheSchwartz. Redis::JobQueue, and Beam::Minion. There are a couple of others too, I think.
That stuff adds quite a lot of administrator load to code and it takes, I argue, an experienced Perl hacker to keep it from creeping into spaghetti. It can be what people need and it certainly unifies reporting and error handling and would probably be the best backend to a web admin system of jobs or user initiated jobs and such but if you already have functional cron scripts you might instead just formalize them. Have them log to the same place. Get them into revision control. Lock down the environment paths and the user that runs them. Rewrite anything too basic or shell-y into Perl. It's up to you of course but consider what you really want to achieve in the end and how much bandwidth/time you have to do it.
In reply to Re: Long-running automation tasks
by Your Mother
in thread Long-running automation tasks
by bfdi533
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |