<br><br><div class="gmail_quote">On Wed, Jan 23, 2013 at 12:54 PM, Andrus, Brian Contractor <span dir="ltr"><<a href="mailto:bdandrus@nps.edu" target="_blank">bdandrus@nps.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Seems to me that would be by design and you need to be aware of it.<br>
-V basically just takes the output of 'env' and sets anything that is set.<br>
Since you already have PBS_* variables, I would expect them to be set already.<br>
<br>
This could be handled by pbs_mom if it were to first sent the -V stuff and then set the PBS_* stuff.<br>
You can do this by iterating through and 'unset' all the PBS_* variables before doing the qsub.<br>
<br>
I tend to rend this moot by highly discouraging the use of -V<br>
It's use makes it difficult to troubleshoot when folks use things like "./a.out" to run their programs.<br>
<br>
<br>
Brian Andrus<br>
ITACS/Research Computing<br>
Naval Postgraduate School<br>
Monterey, California<br>
voice: <a href="tel:831-656-6238" value="+18316566238">831-656-6238</a><br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
> -----Original Message-----<br>
> From: <a href="mailto:torqueusers-bounces@supercluster.org">torqueusers-bounces@supercluster.org</a> [mailto:<a href="mailto:torqueusers-">torqueusers-</a><br>
> <a href="mailto:bounces@supercluster.org">bounces@supercluster.org</a>] On Behalf Of Matthew Britt<br>
> Sent: Tuesday, January 22, 2013 11:22 AM<br>
> To: Torque Users Mailing List<br>
> Subject: [torqueusers] PBS environmental variables and -V<br>
><br>
> Hello everyone. What is the expected behavior in precedence between<br>
> PBS environmental variables and -V when a job is submitted from an<br>
> interactive job. With torque 4.1.4 (and possibly earlier), the variables from<br>
> the environment of the interactive shell are passed along w/ the newly<br>
> submitted job (either interactive or batch). We've seen both PBS_O_HOST<br>
> and PBS_O_WORKDIR be set to values of the first job rather than the<br>
> attributes of the second job.<br>
><br>
> As an example:<br>
><br>
> [msbritt@nyx ~]$ cd bin<br>
> [msbritt@nyx bin]$ pwd<br>
> /home/msbritt/bin<br>
> [msbritt@nyx bin]$ qsub -I -l nodes=1,walltime=5:00 -q flux -A msbritt_flux -<br>
> V<br>
> qsub: waiting for job <a href="http://9445802.nyx.engin.umich.edu" target="_blank">9445802.nyx.engin.umich.edu</a> to start<br>
> qsub: job <a href="http://9445802.nyx.engin.umich.edu" target="_blank">9445802.nyx.engin.umich.edu</a> ready<br>
><br>
> [msbritt@nyx5515 ~]$ echo $PBS_O_WORKDIR<br>
> /home/msbritt/bin<br>
> [msbritt@nyx5515 ~]$ echo $PBS_O_HOST<br>
> <a href="http://nyx.engin.umich.edu" target="_blank">nyx.engin.umich.edu</a><br>
> [msbritt@nyx5515 ~]$ pwd<br>
> /home/msbritt<br>
><br>
> [msbritt@nyx5515 ~]$ qsub -I -l nodes=1,walltime=5:00 -q flux -A<br>
> msbritt_flux -V<br>
> qsub: waiting for job <a href="http://9445813.nyx.engin.umich.edu" target="_blank">9445813.nyx.engin.umich.edu</a> to start<br>
> qsub: job <a href="http://9445813.nyx.engin.umich.edu" target="_blank">9445813.nyx.engin.umich.edu</a> ready<br>
><br>
> [msbritt@nyx5623 ~]$ pwd<br>
> /home/msbritt<br>
> [msbritt@nyx5623 ~]$ echo $PBS_O_WORKDIR<br>
> /home/msbritt/bin (arguably should be /home/msbritt)<br>
> [msbritt@nyx5623 ~]$ echo $PBS_O_HOST<br>
> <a href="http://nyx.engin.umich.edu" target="_blank">nyx.engin.umich.edu</a> (arguably should be nyx5515)<br>
><br>
><br>
> Should -V not read the PBS_O_* variables on job submission or at least be<br>
> overwritten and correctly set in the next job, or should -V trump ?<br>
><br>
> Thanks,<br>
> - Matt<br>
><br>
> --------------------------------------------<br>
> Matthew Britt<br>
> CAEN HPC Group - College of Engineering<br>
> <a href="mailto:msbritt@umich.edu">msbritt@umich.edu</a><br>
></div></div></blockquote><br>what happens when the user sets the PBS_O* variables in the environment to what they want and then TORQUE changes all of them?<br><br>Ken<br></div><br>