The fact is, there are different types of cron but this variable is used only in the case "soft". This is a global var and it should go away. The value should go in settings. The logic should depend on the value of this variable.
On Jan 31, 1:47 pm, Jonathan Lundell <jlund...@pobox.com> wrote: > On Jan 31, 2010, at 11:20 AM, Brian M wrote: > > > Yes, that mostly fixes things. However, you still need an explicit > > test for the @reboot or it won't ever run, check won't have a -1 > > minute in it. I am testing out a modified cron.py with all of the > > fixes we've covered in this thread plus the checks for whether or not > > a task should be run split into its own function for a bit better > > clarity. I will send you a diff after I've had a chance to test > > everything on linux. Right now Windows seems to be working pretty > > well. > > A cosmetic matter (for now, anyway). cron.py says > > # crontype can be 'soft', 'hard', 'external', None > > but widget.py says > > contrib.cron.crontype = 'External' > > For now, anyway, it appears that crontype is either 'soft' or not, as far as > the logic is concerned. -- 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.
