Re: [Toolserver-l] How to silence qsub/qcronsub?

2012-03-16 Thread Dr. Trigon
-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 http:

Re: [Toolserver-l] How to silence qsub/qcronsub?

2012-03-12 Thread DaB.
Hello, At Monday 12 March 2012 17:46:22 DaB. wrote: > Is it now usual behaviour that qcronsub adds all command-line > options to following calls too? no, it is not. But I can not reproduce that here, can you please tell us more details? (in a jira-bug if possible). Sincerly, DaB. -- Userpage:

Re: [Toolserver-l] How to silence qsub/qcronsub?

2012-03-12 Thread Dr. Trigon
-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 optio

Re: [Toolserver-l] How to silence qsub/qcronsub?

2012-03-11 Thread Merlissimo
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

Re: [Toolserver-l] How to silence qsub/qcronsub?

2012-03-08 Thread Platonides
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

Re: [Toolserver-l] How to silence qsub/qcronsub?

2012-03-08 Thread Simon Kågedal Reimer
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 + +++

Re: [Toolserver-l] How to silence qsub/qcronsub?

2012-03-07 Thread Simon Kågedal Reimer
Hi, thanks for the advice! Here is some testing: # Output when things are ok: skagedal@clematis:~/fafafa$ qcronsub ./do_fafafa.sh Your job 1753569 ("Fafafa") has been submitted # Output when things are not ok: skagedal@clematis:~/fafafa$ qcronsub ./do_fififi.sh Unable to read script file because o

Re: [Toolserver-l] How to silence qsub/qcronsub?

2012-03-07 Thread Sumurai8 (DD)
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 > Hi! > > Does

Re: [Toolserver-l] How to silence qsub/qcronsub?

2012-03-07 Thread Platonides
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

[Toolserver-l] How to silence qsub/qcronsub?

2012-03-07 Thread Simon Kågedal Reimer
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 as expected, so I don't want all output silenced. Rega