|
|
|
|
|
The iCk command also accepts environment variables from the command line of the form:
{variable-name} = {value}
These can be used to set environment variables that also affect the behavior of iCk. These environment variables are described in the following table:
Environment variable |
Description |
Comments |
VERBOSITY |
An alternative way to set the internal verbosity flags |
The meanings of the bits are the same as for the value supplied to the -v flag |
SHELL |
Specifies the name of the shell to be used when executing commands |
Default is /bin/sh |
UTMP |
Specifies where the utmp file associated with the system is located |
Value is not used except for debugging purposes |
PATH |
Indicates where iCk finds executable programs |
Default is /bin:/etc/:/usr/bin:/vs/bin:/vs/bin/util:/vs/bin/tools |
When running as a daemon process, iCk accepts a file name, which is the name of the rules file from which it is supposed to operate. If not specified, the default rules file is /vs/etc/iCk.rules.
When iCk is executed with the -c flag or by the alternate name iCkCmd, iCk is run as the command interface to the iCk daemon process.
The following table lists information about other options:
Argument |
Description |
-i |
This option specifies that iCk to run in interactive mode. This causes iCk to generate prompts as it requests information from its standard input. Without the -i flag, iCk silently accepts input from its standard input. This might be useful if used in a shell script. |
-f {file} |
This value causes iCk to read a series of commands from the specified file or device instead of from its standard input |
{cmd}... |
This field causes iCk to use the remaining arguments on the command line as the commands to be sent to the iCk daemon process |
