Hi,
since we changed to Solaris I'm not able to start my perl-script via cron.
1.
I'm using the example given at
https://wiki.toolserver.org/view/Cronsub#cronsub for my cronjob:
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /opt/local/bin/cronsub -s
seth-vdetector % /usr/bin/perl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
seth:
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /opt/local/bin/cronsub -s
seth-vdetector % /usr/bin/perl $HOME/bots/vdetector.pl /dev/null
For a long-running job, you should use -sl. Otherwise your job will be
killed after 6 hours. (This is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. Trigon:
'qsub $HOME/pywikipedia/runbotrun.py -cron'
which is the equivalent to:
'0 2 * * * cronsub -s mainbot $HOME/pywikipedia/runbotrun.py -cron'
These are not equivalent. cronsub does a fair amount of additional processing
on top of
You can run cronsub from the command-line for testing.
;))) easy, simple and straight forward... should be kind
of obvious... :))
Thanks a lot! ;)
- river.
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've made a couple of changes to cronsub in response to some issues reported by
users. Specifically:
* cronsub now requires that the script file be executable, and will raise an
error if it's not. The previous behaviour was that
Op 8 jan 2011, om 03:28 heeft River Tarnell het volgende geschreven:
I've made a couple of changes to cronsub in response to some issues
reported by
users. Specifically:
* cronsub now requires that the script file be executable, and will
raise an
error if it's not. The previous
