Opened 14 years ago
Last modified 10 years ago
#407 new defect
IZ2203: qsub/qrsh shall reject relative pathes with -b y if they can not resolve them with PATH
Reported by: | andreas | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | sge | Version: | 6.1 |
Severity: | Keywords: | clients | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2203]
Issue #: 2203 Platform: All Reporter: andreas (andreas) Component: gridengine OS: All Subcomponent: clients Version: 6.1 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: DEFECT Target milestone: --- Assigned to: roland (roland) QA Contact: roland URL: * Summary: qsub/qrsh shall reject relative pathes with -b y if they can not resolve them with PATH Status whiteboard: Attachments: Issue 2203 blocks: Votes for issue 2203: Opened: Fri Mar 2 04:12:00 -0700 2007 ------------------------ DESCRIPTION: Often Grid Engine end users get job failures when they specify # qsub -b y <relative-path> since then clean job execution depends on PATH environment variable at execution time. Due to this dependency at execution time these cases are hard to analyze and sometimes fixing the problem is not possible at all due to the fact that PATH environment is not set from users $HOME/.profile or $HOME/.login in certain cases. The cases are when actually no shell was started (e.g. -noshell) or when the shell does not source $HOME/.profile or $HOME/.login as it does since it simply does not regard the hyphen ("-") that was specified as arg0 with execv(2). SUGGESTED FIX: When "-b y" is used, relative pathes shall generally be rejected, if the binary/script can not be found already based on the PATH environment at submission time. If the binary/script can be found Grid Engine shall assume that the full path as resolved at client side be valid also at the execution host.
Note: See
TracTickets for help on using
tickets.