Start Examples

The following examples show variations of the start subcommand.

Using the default

% lock_lint start

LockLint's context is established and LL_CONTEXT is set. Then the program identified by $SHELL is executed. Normally, this is your default shell. LockLint subcommands can now be entered. Upon exiting the shell, the LockLint context is removed.

Using a pre-written script

% lock_lint start foo

The LockLint context is established and LL_CONTEXT is set. Then, the command /bin/csh -c foo is executed. This results in executing the C shell command file foo, which contains LockLint commands. Upon completing the execution of the commands in foo by /bin/csh, the LockLint context is removed.

If you use a shell script to start LockLint, insert #! in the first line of the script to define the name of the interpreter that processes that script. For example, to specify the C-shell the first line of the script is:

#! /bin/csh

Starting up with a specific shell

In this case, the user starts LockLint with the Korn shell:

% lock_lint start /bin/ksh

After establishing the LockLint context and setting LL_CONTEXT, the command /bin/ksh is executed. This results in the user interacting with an interactive Korn shell. Upon exiting the Korn shell, the LockLint context is removed.