>
> Sorry I overlooked that.
>>
> Overall I have to say that I have found the scheduler implimentation
excellent. It is very versatile and well thought out. So many thanks for
all your hard work on this and to anyone else who contributed.
Peter
--
Resources:
- http://web2py.com
- http://web
taken directly from the book.
*The first argument of the Scheduler class must be the database to be used
by the scheduler to communicate with the workers. This can be the db of the
app or another dedicated db, perhaps one shared by multiple apps. If you
use SQLite it's recommended to use a sepa
I changed the task to use a flag in a file rather than a flag in the
database, this seems to stop the worker from hanging. So it would seem that
one is well advised to avoid using SQLite within the scheduler unless one
has WAL.
Actually a way that might be safe is to use another database for
Okay thanks Niphlod.
That is a difference between the two installations, the working one has a
later version of sqlite, with WAL enabled.
I will see if I can work around accessing sqlite.
Peter
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2
"active" is the last status detected. If the process is a single one and no
other is checking, the status won't be updated (but you'll notice that
last_heartbeat doesn't get updated).
If there are two processes and one fails, the other one checks for the
last_heartbeat(s) and prunes the record
5 matches
Mail list logo
