On 10/10/2012 10:08 AM, Dave Love wrote:
Orion Poplawski <[email protected]> writes:
That looks good. Any good example starter method scripts that handle
the SGE_STARTER_SHELL_START_MODE and SGE_STARTER_USE_LOGIN_SHELL
variables appropriately when running the shell?
If you mean a general starter that deals with all the possibilities for
shell_start_mode etc., then the example is the built-in starter. See a
long thread fairly recently about starter methods and the environment.
Well, looks like shell_start_mode is deprecated and doesn't do a whole lot
now. As for handling SGE_STARTER_USE_LOGIN_SHELL, this seems to be the
equivalent:
# Start the job
if [ "$SGE_STARTER_USE_LOGIN_SHELL" == true ]
then
shellname=$(basename $SGE_STARTER_SHELL_PATH)
exec -a -${shellname} $SGE_STARTER_SHELL_PATH "$@"
else
exec $SGE_STARTER_SHELL_PATH "$@"
fi
Somewhat funny - it looks like it tries to start the starter_method as a
"login shell", i.e. with a leading "-":
/var/spool/gridengine/castor/active_jobs/27713.1/trace:
10/10/2012 15:43:55 [1744:19855]:
execvp(/usr/share/gridengine/util/dmtcp_starter, "-dmtcp_starter"
"/var/spool/gridengine/castor/job_scripts/27713" "./foo" "7200" "out.qsub")
This doesn't cause any problems for me, though starter scripts that examine $0
might get confused.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder Office FAX: 303-415-9702
3380 Mitchell Lane [email protected]
Boulder, CO 80301 http://www.nwra.com
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
