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 of error: error opening
./do_fififi.sh: No such file or directory
# Piping to -dev/null:
skagedal@clematis:~/fafafa$ qcronsub ./do_fafafa.sh > /dev/null
# Good, nice and quiet.
skagedal@clematis:~/fafafa$ echo $?
0
# And returned zero for success!
skagedal@clematis:~/fafafa$ qcronsub ./do_fafafi.sh > /dev/null
# Hmm, also quiet - qcronsub outputs all messages, even on error, on stdout
skagedal@clematis:~/fafafa$ echo $?
14
# But returns correctly. What about qsub?
skagedal@clematis:~/fafafa$ qsub ./do_fafafa.sh > /dev/null
skagedal@clematis:~/fafafa$ qsub ./do_fififi.sh > /dev/null
Unable to read script file because of error: error opening
./do_fififi.sh: No such file or directory
skagedal@clematis:~/fafafa$ echo $?
14
# Works as expected!
# How about the -o option? Let's try qcronsub.
skagedal@clematis:~/fafafa$ qcronsub ./do_fafafa.sh -o myfile.txt
Your job 1753616 ("Fafafa") has been submitted
# Nope. qsub then?
skagedal@clematis:~/fafafa$ qsub ./do_fafafa.sh -o myfile.txt
Your job 1753617 ("Fafafa") has been submitted
# Nope, that options seems to do something else.


So, in summary, I believe changing "qcronsub fafafa.sh" (which I
currently have in my cronie) to "qsub fafafa.sh > /dev/null" will give
me the behavior I want. However, without the added qcronsub uniqueness
functionality, which is ok for my purposes. (as Platonides said, I'd
get a mail from cronie anyway when qcronsub failed - but a less
descriptive e-mail...)

Merlissimo, I would suggest changing qcronsub so that it outputs on
stderr when return code is not 0. Thanks!

Regards, Simon

On Wed, Mar 7, 2012 at 10:02 PM, Sumurai8 (DD) <sumur...@gmail.com> wrote:
> 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 <skage...@gmail.com>
>>
>> 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.
>>
>> Regards,
>> Simon Kågedal Reimer (skagedal)
>>
>>
>> _______________________________________________
>> Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
>> https://lists.wikimedia.org/mailman/listinfo/toolserver-l
>> Posting guidelines for this list:
>> https://wiki.toolserver.org/view/Mailing_list_etiquette
>
>
>
> _______________________________________________
> Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/toolserver-l
> Posting guidelines for this list:
> https://wiki.toolserver.org/view/Mailing_list_etiquette

_______________________________________________
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

Reply via email to