On Feb 8, 8:22 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > On Feb 8, 11:43 am, AchipA <attila.cs...@gmail.com> wrote: > > > 1) ok > > 2) this would be the cron.master file. Sadly, it must be a file as > > otherwise multiprocess setups (like wsgi) would trip over each other. > > ok. but there should be a function to check its status. > to make sure... what I mean is a way to check not if it is running > "right now" but if a) it was set to run; and b) it failed somehow.
Detecting fails is tricky, sure, within the cron code we can try/catch (I'm under the impression I do that a lot more that you'd like :), but it's hard to tell why exactly something we called failed, due to cron problems, parametrization, some unrelated error, etc. Improving stderr handling could improve this, but that is also an issue on it's own. > > 3) I'm thinking of deprecating posttasks in favor of being able to > > daisy-chain controllers. So you would not have posttasks, but you > > could specify a controller that would be called automatically after > > the current controller is finished. That would be a lot cleaner > > but would keep the functionality. > > Look into tools.py @completion. Not quite what you want but perhaps > you can keep the syntax. Will take a look. -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
