Hi,
is there an option to have qsub/qcronsub mail me the output of a command instead of writing it to disk? Something simi- lar to regular cron/at?
TIA, Tim
Hi Tim,
Please see the documentation on Toolserver wiki [1] to set this up. It uses a command of -m with another variable depending on when you want mail sent.
[1] https://wiki.toolserver.org/view/Batch_job_scheduling#arguments_to_qsub/qcro...
Cheers,
James
On 01/10/2012, at 9:05 PM, Tim Landscheidt tim@tim-landscheidt.de wrote:
Hi,
is there an option to have qsub/qcronsub mail me the output of a command instead of writing it to disk? Something simi- lar to regular cron/at?
TIA, Tim
(anonymous) wrote:
Please see the documentation on Toolserver wiki [1] to set this up. It uses a command of -m with another variable depending on when you want mail sent.
[1] https://wiki.toolserver.org/view/Batch_job_scheduling#arguments_to_qsub/qcro... [...]
That just sends notifications about the job's status, not the job's output itself.
Tim
On 01/10/12 13:21, Tim Landscheidt wrote:
(anonymous) wrote:
Please see the documentation on Toolserver wiki [1] to set this up. It uses a command of -m with another variable depending on when you want mail sent.
[1] https://wiki.toolserver.org/view/Batch_job_scheduling#arguments_to_qsub/qcro... [...]
That just sends notifications about the job's status, not the job's output itself.
Tim
No, there's no such option. I looked into it recently. We could get that by adding a final script which mails the user the output file if qstat -j $JOB_ID | grep -q mail_options:.*e.
(anonymous) wrote:
Please see the documentation on Toolserver wiki [1] to set this up. It uses a command of -m with another variable depending on when you want mail sent.
[1] https://wiki.toolserver.org/view/Batch_job_scheduling#arguments_to_qsub/qcro... [...]
That just sends notifications about the job's status, not the job's output itself.
No, there's no such option. I looked into it recently. We could get that by adding a final script which mails the user the output file if qstat -j $JOB_ID | grep -q mail_options:.*e.
Thanks. I don't want to fiddle to much with SGE's in- testines, so I will probably either use "| mail timl" in my script or have my MUA insert the log in the status mail.
I looked if I could submit this totally fascinating and innovative idea of mailing the output as a RFE upstream, but amazingly I didn't see a bugtracker at Oracle :-). I would even have had another idea: Impromptu jobs à la "echo true | at now" :-).
Tim
On 01/10/12 14:19, Tim Landscheidt wrote:
Thanks. I don't want to fiddle to much with SGE's in- testines, so I will probably either use "| mail timl" in my script or have my MUA insert the log in the status mail.
I looked if I could submit this totally fascinating and innovative idea of mailing the output as a RFE upstream, but amazingly I didn't see a bugtracker at Oracle :-). I would even have had another idea: Impromptu jobs à la "echo true | at now" :-).
Tim
Oracle closed-sourced it. There are a number of forks. Quick link: http://gridengine.org/blog/2011/11/23/what-now/
(anonymous) wrote:
Thanks. I don't want to fiddle to much with SGE's in- testines, so I will probably either use "| mail timl" in my script or have my MUA insert the log in the status mail.
I looked if I could submit this totally fascinating and innovative idea of mailing the output as a RFE upstream, but amazingly I didn't see a bugtracker at Oracle :-). I would even have had another idea: Impromptu jobs à la "echo true | at now" :-).
Oracle closed-sourced it. There are a number of forks. Quick link: http://gridengine.org/blog/2011/11/23/what-now/
If these two issues are the only things missing in SGE, I think we can stay with it :-).
Tim
Am 01.10.2012 17:33, schrieb Tim Landscheidt:
(anonymous) wrote:
Thanks. I don't want to fiddle to much with SGE's in- testines, so I will probably either use "| mail timl" in my script or have my MUA insert the log in the status mail.
I looked if I could submit this totally fascinating and innovative idea of mailing the output as a RFE upstream, but amazingly I didn't see a bugtracker at Oracle :-). I would even have had another idea: Impromptu jobs à la "echo true | at now" :-).
Oracle closed-sourced it. There are a number of forks. Quick link: http://gridengine.org/blog/2011/11/23/what-now/
If these two issues are the only things missing in SGE, I think we can stay with it :-).
Tim
No, we are using an open source version based on SGE 6.2u5 patch 2 which was the last open source version by oracle (so for documentation refer to this version). I used Grid Engine 2011.11p1 but i also added some additional bug patches and special modifications for our toolserver version.
But the mail feature you requested could be implemented without modifying any source code by our epilog script. Just open a jira ticket and i will think about this feature.
Merlissimo
(anonymous) wrote:
Thanks. I don't want to fiddle to much with SGE's in- testines, so I will probably either use "| mail timl" in my script or have my MUA insert the log in the status mail.
I looked if I could submit this totally fascinating and innovative idea of mailing the output as a RFE upstream, but amazingly I didn't see a bugtracker at Oracle :-). I would even have had another idea: Impromptu jobs à la "echo true | at now" :-).
Oracle closed-sourced it. There are a number of forks. Quick link: http://gridengine.org/blog/2011/11/23/what-now/
If these two issues are the only things missing in SGE, I think we can stay with it :-).
No, we are using an open source version based on SGE 6.2u5 patch 2 which was the last open source version by oracle (so for documentation refer to this version). I used Grid Engine 2011.11p1 but i also added some additional bug patches and special modifications for our toolserver version.
Oh, that's nice. Is the source available somewhere?
But the mail feature you requested could be implemented without modifying any source code by our epilog script. Just open a jira ticket and i will think about this feature.
I've opened TS-1530 and TS-1531; please feel free to assign them to you.
Tim
I wrote:
Thanks. I don't want to fiddle to much with SGE's in- testines, so I will probably either use "| mail timl" in my script or have my MUA insert the log in the status mail.
I looked if I could submit this totally fascinating and innovative idea of mailing the output as a RFE upstream, but amazingly I didn't see a bugtracker at Oracle :-). I would even have had another idea: Impromptu jobs à la "echo true | at now" :-).
Oracle closed-sourced it. There are a number of forks. Quick link: http://gridengine.org/blog/2011/11/23/what-now/
If these two issues are the only things missing in SGE, I think we can stay with it :-).
No, we are using an open source version based on SGE 6.2u5 patch 2 which was the last open source version by oracle (so for documentation refer to this version). I used Grid Engine 2011.11p1 but i also added some additional bug patches and special modifications for our toolserver version.
Oh, that's nice. Is the source available somewhere? [...]
Merlissimo replied on IRC that the source is at /mnt/user-store/sge and that binaries for Solaris and Linux 2.6 were compiled on Solaris boxes. /sge is shared between hosts and also contains the master spool. So if someone wants to tackle TS-963, there you are :-).
Tim
toolserver-l@lists.wikimedia.org