Difference between revisions of "GLExec"

From PDP/Grid Wiki
Jump to navigationJump to search
Line 19: Line 19:
 
** [[GLExec TransientPilotJobs]] describes how you may go about managing a '''target''' workload's '''directory''' in '''Pilot Job Frameworks'''.
 
** [[GLExec TransientPilotJobs]] describes how you may go about managing a '''target''' workload's '''directory''' in '''Pilot Job Frameworks'''.
 
** [[GLExec Environment Wrap and Unwrap scripts]] describes how you can '''preserve''' the '''environment''' variables between the calling process of gLExec and the user switched side of gLExec. For example: to preserve the environment variables from a Pilot Job Framework, through gLExec and into Pilot Job Payload.
 
** [[GLExec Environment Wrap and Unwrap scripts]] describes how you can '''preserve''' the '''environment''' variables between the calling process of gLExec and the user switched side of gLExec. For example: to preserve the environment variables from a Pilot Job Framework, through gLExec and into Pilot Job Payload.
** [[Building gLExec from src rpm]]. How to do it as admin or user.
+
** [[Building gLExec from src rpm]] How to build gLExec from a .src.rpm
  
 
* [[FAQs and misconceptions about gLExec]]
 
* [[FAQs and misconceptions about gLExec]]

Revision as of 16:19, 1 March 2010

Multi User Pilot Job with CE & WN

gLExec is a program that acts as a light-weight 'gatekeeper'. gLExec takes Grid credentials as input. gLExec takes the local site policy into account to authenticate and authorize the credentials. gLExec will switch to a new execution sandbox and execute the given command as the switched identity. gLExec is also capable of functioning as a light-weight control point which offers a binary yes/no result called the logging-only mode.

Deployment: Installation and setups

How To's and FAQ

  • To help you master gLExec's security:

Documentation