[torqueusers] Newbie Questions.

Macbeth R. macbeth.rene at gmail.com
Mon Oct 7 11:17:58 MDT 2013


Thanks, for the tips, right now I made a script that acts as qstat it just
reads de "account_string" slot an put it on the list as a comment for the
job, so they are viewing the comment whenever the make a qstat...

Maybe I keep it that way then.

Thanks.


On Mon, Oct 7, 2013 at 11:15 AM, Sreedhar Manchu <sm4082 at nyu.edu> wrote:

> I don't know whether there is an option for this but what I would do is to
> show these comments on the standard output when they submit jobs it self.
> This can be done through qsub wrapper or an alias bash script to qsub that
> simple does this on all the login nodes. Of course, the only problem with
> this approach is that users might forget about it after submitting the job.
>
> Sreedhar.
>
> On Oct 7, 2013, at 11:59 AM, "Macbeth R." <macbeth.rene at gmail.com> wrote:
>
> Jumm.. I made a mistake on my last message, didn't send it full.
>
> Thanks for de tip, I will try it.
> I want to store some comments in the JOB, like "Please dont put any other
> job, with High priority than this"
> Or "Please call me when this finish" whatever... just store some comments
> in the job, I dont want to use a secondary database for this, so I had been
> using the "acount_string" slot to store them.. altought that option is not
> for that.
>
> But I will use it for its real purpose soon, so I was wondering if there
> is a way to store string comments in the job?
>
>
>
>
>
> On Sat, Oct 5, 2013 at 6:30 PM, Macbeth R. <macbeth.rene at gmail.com> wrote:
>
>> Thanks for de tip, I will try it.
>>  I want to store some comments in the JOB, like "Please
>>
>>
>> On Fri, Oct 4, 2013 at 6:46 PM, Sreedhar Manchu <sm4082 at nyu.edu> wrote:
>>
>>> Hi Macbeth,
>>>
>>> I am not sure I understand your first question.
>>>
>>> For the second question, I'm not sure whether it is possible through
>>> #PBS directives. If I understand right, job array is just a convenience and
>>> makes it possible for us to submit many jobs together. But all these jobs
>>> are still treated as different jobs from each other. If this is not the
>>> case, then all the jobs in the array would have to run at the same time
>>> which makes it impossible in many scenarios.
>>>
>>> On the other hand, I'd simply take of #PBS directives that would send
>>> emails on abort, begin and end (#PBS -M and #PBS -m) and then add a code in
>>> the script to send an email when the PBS_ARRAYID is zero. Something like
>>> this would do:
>>>
>>> if [ $PBS_ARRAYID -eq 0 ];then
>>> use sendmail to send an email to your email id here.
>>> fi
>>>
>>> May be there is a better solution.
>>>
>>> Sreedhar.
>>>
>>>
>>> On Oct 4, 2013, at 2:28 PM, Macbeth R. <macbeth.rene at gmail.com> wrote:
>>>
>>> Hi, I had been using torque 3.0.6, on Centos 6.4, and everything is
>>> working great :D
>>>
>>> I had some questions, thanks in advance is someone points me in the
>>> right direction.
>>>
>>> 1- Is there a way to put comments on jobs?? or a trick? I was trying to
>>> use the "acount_string" option to store some comments there, sucefully, but
>>> I might be needing this option for its real purpose soon, any tips?
>>>
>>> 2- How can I get a email notification per job array, and not per job, ?
>>> Im sending job arrays of thousands of jobs, I dont want thousands of
>>> emails, on my Inbox.
>>>
>>>
>>> Thanks!!
>>>
>>> Macbeth Rene R.
>>>
>>>
>>>
>>> --
>>> CONFIDENTIALITY NOTICE: This e-mail message is intended only for the
>>> above-mentioned recipient(s). Its content is confidential. If you have
>>> received this e-mail by error, please notify us immediately and delete it
>>> without making a copy, nor disclosing its content, nor taking any action
>>> based thereon. Thank you.
>>> _______________________________________________
>>> torqueusers mailing list
>>> torqueusers at supercluster.org
>>> http://www.supercluster.org/mailman/listinfo/torqueusers
>>>
>>>
>>>
>>> _______________________________________________
>>> torqueusers mailing list
>>> torqueusers at supercluster.org
>>> http://www.supercluster.org/mailman/listinfo/torqueusers
>>>
>>>
>>
>>
>> --
>> CONFIDENTIALITY NOTICE: This e-mail message is intended only for the
>> above-mentioned recipient(s). Its content is confidential. If you have
>> received this e-mail by error, please notify us immediately and delete it
>> without making a copy, nor disclosing its content, nor taking any action
>> based thereon. Thank you.
>>
>
>
>
> --
> CONFIDENTIALITY NOTICE: This e-mail message is intended only for the
> above-mentioned recipient(s). Its content is confidential. If you have
> received this e-mail by error, please notify us immediately and delete it
> without making a copy, nor disclosing its content, nor taking any action
> based thereon. Thank you.
> _______________________________________________
> torqueusers mailing list
> torqueusers at supercluster.org
> http://www.supercluster.org/mailman/listinfo/torqueusers
>
>
>
> _______________________________________________
> torqueusers mailing list
> torqueusers at supercluster.org
> http://www.supercluster.org/mailman/listinfo/torqueusers
>
>


-- 
CONFIDENTIALITY NOTICE: This e-mail message is intended only for the
above-mentioned recipient(s). Its content is confidential. If you have
received this e-mail by error, please notify us immediately and delete it
without making a copy, nor disclosing its content, nor taking any action
based thereon. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.supercluster.org/pipermail/torqueusers/attachments/20131007/4775abd9/attachment-0001.html 


More information about the torqueusers mailing list