[GE issues] [Issue 222] qrsh: move info from environment variables to job object

pollinger harald.pollinger at sun.com
Thu Jun 25 15:18:03 BST 2009


------- Additional comments from pollinger at sunsource.net Thu Jun 25 07:18:01 -0700 2009 -------

QRSH_WRAPPER is documented in the submit(1) man page:
"If the environment variable QRSH_WRAPPER is set when qrsh is invoked, the command interpreter pointed to by QRSH_WRAPPER will be executed
to run qrsh commands instead of the users login shell or any shell specified in the qrsh command-line."
"qrsh" puts it in the job environment, the "execd" and the "shepherd" just forward it with the rest of the environment, only the
"qrsh_starter" and "qmake" evaluate it and remove it from the job environment. So if we want to remove the QRSH_WRAPPER from the job
environment and put it to the job object in the whole Grid Engine, we need some means to hand over the QRSH_WRAPPER from the "shepherd" to
the "qrsh_starter" and "qmake" outside of the environment file.

QRSH_COMMAND is not documented in the man pages.
QRSH_COMMAND is generated by the "qrsh" client and evaluated by "qrsh_starter" and by the "builtin_starter" of the "shepherd". Here we also
need a way to hand over QRSH_COMMAND to the "qrsh_starter" outside of the environment file in order to remove it from the job environment.

QRSH_PORT is not documented in the man pages.
QRSH_PORT is generated by the "qrsh" client and contains "$HOSTNAME:$PORT". It's evaluated by the "execd", but it's not removed from the job
environment, so a "qrsh echo \$QRSH_PORT" prints both the host and the port of the qrsh client (for builtin IJS).
As it's not documented, it should be no problem to remove it from the job environment and hand it over in the job object.


To unsubscribe from this discussion, e-mail: [issues-unsubscribe at gridengine.sunsource.net].

More information about the gridengine-users mailing list