-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I did not open an JIRA bug because it vanished again... so; SOLVED.
But if someone is interessted in details:
http://toolserver.org/~drtrigon/DrTrigonBot/mainbot.log.2012-03-11
http://toolserver.org/~drtrigon/DrTrigonBot/mainbot.log.2012-03-12
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is it now usual behaviour that qcronsub adds all command-line
options to following calls too?
qcronsub [some options] script.py [other options]
used to call
script.py [other options]
but now it calls
script.py [some options] script.py [other
Hi,
i have changed qcronsub, so that the long output about successful submit and
output about rejection because job already queued is now suppressed. All other
output (e.g. warning) is still shown.
Using -verbose enables all output as it was before my change. If you are using
-terse (maybe
Ah, sorry, that didn't work - can't run qsub directly from cronie
since we need to set some environment variables etc.
Suggesting instead this patch to qcronsub (patched version at
/home/skagedal/local/bin/qcronsub2):
--- /sge62/bin/sol-amd64/qcronsub 2012-03-01 00:24:30.297917000 +
On 08/03/12 09:32, Simon Kågedal Reimer wrote:
Ah, sorry, that didn't work - can't run qsub directly from cronie
since we need to set some environment variables etc.
Just
SGE_ROOT=/sge62 qsub $HOME/do_fififi.sh
would work.
But changing qcronsub is indeed appropiate.
Suggesting instead this
On 07/03/12 15:59, Simon Kågedal Reimer wrote:
Hi!
Does anyone have a solution for making qsub/qcronsub not say Your job
... has been submitted to standard output?
Been getting a lot of e-mails from cronie lately...
I *do* of course want it to say something when things are not working
Hi,
I think setting the -o (output) parameter to /dev/null while omitting the
-e (errors) and the -j (merging errors output) parameter should only log
errors. See
https://wiki.toolserver.org/view/Job_scheduling#arguments_to_qsub/qcronsub
Sumurai8
2012/3/7 Simon Kågedal Reimer
