|
msiExecCmd |
( |
msParam_t * |
inpParam1, |
|
|
msParam_t * |
inpParam2, |
|
|
msParam_t * |
inpParam3, |
|
|
msParam_t * |
inpParam4, |
|
|
msParam_t * |
inpParam5, |
|
|
msParam_t * |
outParam, |
|
|
ruleExecInfo_t * |
rei | |
|
) |
| | |
- Description:
- This microservice requests the client to call a rcExecCmd API to fork and execute a command that resides in the server/ibn/cmd directory.
- Module:
- core
- Since:
- pre-2.1
- Author:
- Michael Wan
- Date:
- 2007-05-08
- Note:
- This call does not require client interaction, which means it can be used through rcExecMyRule (irule) or internally by the server.
- Example Usage:
- See clients/icommands/test/rules3.0/
- Parameters:
-
[in] | inpParam1 | - a ExecCmd_MS_T or a STR_MS_T which specify the command (cmd) to execute. |
[in] | inpParam2 | - Optional - a STR_MS_T which specifies the argv (cmdArgv) of the command |
[in] | inpParam3 | - Optional - a STR_MS_T which specifies the host address (execAddr) to execute to command. |
[in] | inpParam4 | - Optional - a STR_MS_T which specifies an iRODS file path (hintPath). The command will be executed on the host where this file is stored. |
[in] | inpParam5 | - Optional - A INT_MS_T or a STR_MS_T. If it is greater than zero, the resolved physical path from the logical hintPath (inpParam4) will be used as the first argument the command. |
[out] | outParam | - a ExecCmdOut_MS_T containing the status of the command execution and the stdout/strerr output. |
[in,out] | rei | - The RuleExecInfo structure that is automatically handled by the rule engine. The user does not include rei as a parameter in the rule invocation. |
- Session Variables Used:
- none
- Session Variables Modified:
- none
- iCAT Attributes Used:
- none
- iCAT Attributes Modified:
- none
- Side Effect:
- none
- Returns:
- integer
- Return values:
-
- Precondition:
- none
- Postcondition:
- none
- See also:
- none
Definition at line 3003 of file reDataObjOpr.c.
|