On 26/07/2011 00:00, Rowdy wrote:
Greeting.
Different time zone perhaps?
fetch_m_data is expected to run at 06:30, but runs at 12:30 (= +6 hours).
this time a ticket is not necessary ;)
the server that runs my web2py is a virtual machine, the date command
gave the correct date info but I di
Manuele Pesenti wrote:
dear all,
I have a strange problem with cron it seams it does not respect what I
have eritten in crontab... this is my crontab:
30 6 * * * root *cron/fetch_m_data
0 7 * * * root *default/send_mail_msg
30 14 * * * root *cron/fetch_x_data
0 21 * * * root *cron/fetch_m_
On 25/07/2011 14:33, Massimo Di Pierro wrote:
Please open a ticket. Does it behave better is 30 6 * and 30 14* are
replaced by 0 6 * and 0 14 *?
can you tell me how to open a ticket?
the fact is that the same application runs correctly in my local laptop
(Debian testing) and not on the produc
Please open a ticket. Does it behave better is 30 6 * and 30 14* are
replaced by 0 6 * and 0 14 *?
On Jul 25, 6:22 am, Manuele Pesenti wrote:
> dear all,
> I have a strange problem with cron it seams it does not respect what I
> have eritten in crontab... this is my crontab:
>
> 30 6 * * * root
Turns out @reboot only worked with extcron. I modified the cron.py so
that now it should work with hardcron (the default) and softcron too.
The fix is in trunk.
Would you please test it and see if I did not break anything?
Massimo
On Jan 25, 5:48 pm, Auden RovelleQuartz wrote:
> Hello,
>
> The
I will try check this asap.
On Jan 25, 5:48 pm, Auden RovelleQuartz wrote:
> Hello,
>
> The cron feature does not seem to work for me. Any insights?
>
> Here is some information:
>
> at this
> URL,http://127.0.0.1:8000/admin/default/edit/oves_beta_001x2auden/cron/cr...,
> this is what I have
>
6 matches
Mail list logo
