Table of Contents

Description

Use this option to edit the stop script that will be executed at service shutdown. The script is unique and uses the configuration file (full name) to select commands to be executed at guest shutdown (selected by "case in...").

If the script does not exist, it will be generated automatically based on existing guests list and will by default do nothing except preparing the script skeleton with commands using the provided script examples to perform the shutdown via either "expect", "rsh" or "ssh". Newly added virtual machines will have their "case" added to the script when it will be edited.

To be able to perform a clean shutdown of your Tru64 or OpenVMS virtual machine, you will have either to use the provided scripts (see above) or to add your own shutdown scripts.

If you plan to use the "expect" utility, please read Tips and Tricks - Shutdown guests with Expect tool for more.

Basic knowledge of shell programming is needed to implement the clean shutdown / stop script.

Options

TO BE CONTINUED

Explanation on the example file

Example with SSH, Tru64 guest

An ssh trust between the CHARON Linux server and the Tru64 guest must have been previously configured in order to use this method. See Tips and Tricks for help to setup the trust.

1. Check the guest can be reached via "ssh" (adapt the ConnectTimeout value to your needs), if yes, issue the shutdown command, wait a few seconds and check if the guest can be "pinged" and repeat with an interval of 5 seconds. If the guest cannot be pinged, assume the shutdown procedure is complete
2. Kill the emulator process (Red Hat Enterprise Linux 6.x) or use the service kill command (RHEL 7.x and CentOS 7.x). Note: the shutdown commands does not power off nor stop the emulator process, that's why this operation is needed
3. Report the stop information within the guest log file

Example with SSH, OpenVMS guest

An ssh trust between the CHARON Linux server and the OpenVMS guest must have been previously configured in order to use this method. See Tips and Tricks for help to setup the trust.

1. Check the guest can be pinged (an "ssh" command as for the Tru64 example above can also be used), if yes, issue the shutdown command, wait a few seconds and check if the guest can be "pinged" and repeat with an interval of 5 seconds. If the guest cannot be pinged, assume the shutdown procedure is complete
2. Kill the emulator process (Red Hat Enterprise Linux 6.x) or use the service kill command (RHEL 7.x and CentOS 7.x). Note: the shutdown commands does not power off nor stop the emulator process, that's why this operation is needed
3. Report the stop information within the guest log file

Example with Expect tool, Tru64 guest

1. Check if there's an active connection to the console on the local host, kill if any.
   Reminder: If the console is locked from an external connection or if the prompt is not detected after sending a carriage return, the expect script will fail.
2. Replace the user (EXPUSR), password (EXPPWD) and shell prompt (EXPPRT) with the ones corresponding to your guest (shell prompt is used to determine if a user is logged on the console)
3. Execute the "expect" script and report all output to /opt/charon/log/console.stop.<guest name>.log. Note: no need to kill the emulator process here as the "power off" command is executed.

Example with Expect tool, AXP VMS guest

1. Check if there's an active connection to the console on the local host, kill if any.
   Reminder: If the console is locked from an external connection or if the prompt is not detected after sending a carriage return, the expect script will fail.
2. Replace the user (EXPUSR), password (EXPPWD) and shell prompt (EXPPRT) with the ones corresponding to your guest (shell prompt is used to determine if a user is logged on the console)
3. Execute the "expect" script and report all output to /opt/charon/log/console.stop.<guest name>.log. No need to kill the emulator process here as the "power off" command is executed.

Example with Expect tool, VAX VMS guest

1. Check if there's an active connection to the console on the local host, kill if any.
   Reminder: If the console is locked from an external connection or if the prompt is not detected after sending a carriage return, the expect script will fail.
2. Replace the user (EXPUSR), password (EXPPWD) and shell prompt (EXPPRT) with the ones corresponding to your guest (shell prompt is used to determine if a user is logged on the console)
3. Execute the "expect" script and report all output to /opt/charon/log/console.stop.<guest name>.log.
   1. VAX systems have no "power off" command so the F6 key will be sent.
   2. The F6 key can be enabled or not in the configuration file. The expect script will send it if the "power off" command fails and if F6 operation fails, it will exit with return code 9 meaning the emulator process will have to be killed.
   3. If the "expect" script returns the error code 9, this means the F6 key is not defined in the configuration file and then the emulator process must be killed
   4. Report the stop information within the guest log file

Optional guest display status script

It is possible to create a script, "/opt/charon/utils/charon_gstart.chkrun" (an example is provided in the 'charon_gstart.chkrun.example' file) that will add a status line while displaying the guests list for running guests only. This script, if needed, has to be created manually and must be executable.

This status line is the result of the command you executed for that guest (known by its configuration file), for example a ping, an ssh command displaying uptime (Tru64) or boottime (OpenVMS).

Display output example:

Script example:

In this example, we'll use "ssh" to display the guest "uptime" and the result of the "uname -nr" command (name of the node + release number of the operating system)

The last 2 lines are mandatory

Example file provided (contains example for Tru64 and OpenVMS):

The example file is "/opt/charon/utils/charon_gstart.chkrun.example".