Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
excludeTable of Contents

Description

This Use this option will allow you 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").

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. (warning) Guests added after script creation will have to be inserted manually.

To be able to perform a clean shutdown of your Tru64 or VMS OpenVMS virtual machine, you will have either to add your own shutdown scripts or to get examples provided in the "charon_gstart.stop.example" script located in the "/opt/charon/utils" folder.

...

  • "ssh" will require a trust to be created between the Linux server and the Tru64 or OpenVMS guest.

  • "expect" will require you pass user and password to the script to enable it to connect to the OPA0 console via 'telnet' and execute the shutdown commands. The "guest_shutdown.exp" script can perform operations to log off a user connected on the console (if the prompt is detected), enter a username/password to login (if "login:" or "username:" is detected), execute the shutdown command (if the prompt is detected) and detect the SRM prompt (>>>) to issue the "power off" command (AXP) or send the F6 key (VAX) if enabled.
    • Note any local existing connection to the console will has to be killed before executing the expect script.
    • (warning) 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.

...

(lightbulb) An ssh trust between the CHARON Linux server and the Tru64 guest must have been previously configured in order to use this optionmethod.

  • Update the configuration file name
  • Replace the existing hostname "pluto" with your Tru64 guest hostname

...

Example with Expect tool, Tru64 guest, variant for systemd

Status
colourRed
titleto do

...

This example is quite the same as the one above except the "expect" script messages will be made available to the service status.

You will have here to replace Replace the user (1), password (2) and shell prompt (3) with the ones corresponding to your guest (shell prompt is used to determine if a user is logged on the console)

...

Example with Expect tool, AXP VMS guest

You will have here to replace Replace the user (1), password (2) and shell prompt (3) with the ones corresponding to your guest (shell prompt is used to determine if a user is logged on the console)

...

Example with Expect tool, VAX VMS guest

You will have here to replace Replace the user (1), password (2) and shell prompt (3) with the ones corresponding to your guest (shell prompt is used to determine if a user is logged on the console)

...

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.

...

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

Image Added

(info) Example file is: "/opt/charon/utils/charon_gstart.chkrun.example"Image Removed

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc