The Linux operating system has various trace facilities that are useful in troubleshooting Vector.

Invoking a Bourne shell with the -x option causes each shell command to be printed before it is executed. This is especially useful for diagnosing problems with installation shell scripts.

To use this trace on the Vector shutdown script, call the Bourne shell (or Korn shell) with the -x option, passing the name ingstop as the script to be executed:

This option can only be used with Linux shell scripts, not with binary executables.

If you are in doubt as to whether a program or command is a binary or shell script, type:

Linux replies with “commands text,” “ASCII text,” or “executable shell script” if it is an executable shell script. Otherwise the file command returns a message specific to your machine—something like demand paged executable and possibly the designated chip on which it was compiled to run.

Some Linux platforms (such as Sun) provide a facility to trace system calls as they are made by a process. To invoke it, enter trace at the operating system prompt.

To ensure that any new errors written to the Vector error log file are displayed on the terminal screen, issue the following command at the terminal.

To continuously monitor the activities of the recovery process (dmfrcp), issue this command: