Custom Query (431 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (139 - 141 of 431)

Ticket Resolution Summary Owner Reporter
#1328 fixed IZ3296: Pseudo variable ~ and ~user for qsub -o/-e will crash the execd Dave Love <d.love@…> reuti
Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=3296]

Issue #:  3296
Summary:  Pseudo variable ~ and ~user for qsub -o/-e will crash the execd
Component:  gridengine
Version:  6.2u5 
Platform:  All 
URL:   
OS/Version:  All 
Status:  NEW
Status whiteboard:   
Keywords:   
Resolution:   
Issue type:  DEFECT 
Priority:  P3 
Subcomponent:  clients 
Assigned to:  roland 
Reported by:  reuti

------- Additional comments from reuti@sunsource.net Fri Dec 10 09:14:50 -0800 2010 ------- 

According to the man page of `qsub`, it's valid to use ~ and ~user for the -o
and -e switches. I.e. for the location of the output and error files. Putting this into a job script using either:

#$ -o ~ #$ -o ~reuti

will crash the execd. According to the messages file it's getting a wrong
cryptic username:

12/10/2010 18:06:26| main|pc15370|E|invalid user name
""/gH)ESC^H^\e^]^H250377364337350267@361跨373h233363277yqܷ@361跨373`341^]^H260 233363277300233<U+FF21B>363277

Specifying a file instead of a directory:

#$ -o ~/myoutput

will also not work, as it puts the job in error state, but the execd won't be
killed in this case.

Same is happening when used on the command line while using quotes to avoid
expansion by the shell of these shortcuts.
#1327 fixed qsched needs a man page dlove
#1326 fixed Expand extra variables in external program templates dlove
Description

Extra variables should be expanded in templates for external commands, such as prolog, pe starter, and remote starters (which currently don't seem to have the expansion at all). This should probably be at least $sge_root, $sge_cell, $arch, to aid finding the command.

This may be complicated, for instance, by the check for things like rsh_daemon being executables.

Note: See TracQuery for help on using queries.