Exit codes of gLExec

Upon Success

Upon successful execution of a program, the return value from gLExec will simply be the return value of the command that was executed.

On Error

The error code that glexec returns:

201 - client error, which includes:

• no proxy is provided
• wrong proxy permissions
• target location is not accessible
• the binary to execute does not exist
• the mapped user has no rigths to execute the binary when GLEXEC_CLIENT_CERT is not set

202 - system error

• glexec.conf is not present or malformed
• lcas or lcmaps initialization failure, can be obtained moving the lcas/lcmaps db files.

203 - authorization error

• user is not whitelisted
• local lcas authorization failure
• user banned by the SCAS server
• lcmaps failure on the scas server
• SCAS server not running
• network cable unplugged on the SCAS server host.

204 - exit code of the called application overlap with the previous ones

• application called by glexec exit with code 201, 202, 203 or 204

126 - Shell returns that the executable can’t be executed:

• This error code is triggered when the execv() call failed to execute the command, because of permission, execution or system problems found during the call for the executable that was tried to be set up. The shell code is not caught, but forwarded as an error code from the actual child process.