Table of contents
Important note
This document applies to Linux Toolkit version 1.44, dated March, 25th 2016
Kit download
To download the kit, you must issue a request via email to the Stromasys support team (support@stromasys.com) or ask your reseller
Prerequisites
- Basic knowledge of Unix commands
- Basic knowledge of CHARON products
CHARON qualified versions:
CHARON-AXP V4.4 Build 147-07
CHARON-AXP V4.5 Build 155-05 minimum
CHARON-AXP V4.6 Build 166-03 minimum
CHARON-AXP V4.7 Build 171-01 minimum
CHARON-VAX V4.6 Build 165-02 minimum
CHARON-VAX V4.7 Build 171-01 minimum
Scripts have been tested and validated on the following Linux distributions/versions:
Fedora 20, 21 and 22
Red Hat Enterprise Linux Server release 6.2 to 6.6
Red Hat Enterprise Linux Server release 7 and 7.2
- Some packages have to be installed on the CHARON server:
- Mandatory packages:
sendmail
→ mandatorybc
→ mandatory
- Recommended packages:
telnet
→ recommended for connection from the CHARON server to the virtual machine consoleexpect
→ recommended ifssh
cannot be used to execute shutdown commands from the consolessh
→ recommended for executing shutdown commands with trusted connection between the CHARON server and the CHARON virtual machineevince
→ recommended for reading online documentationscreen
→ recommended, mandatory for CHARON-AXP V4.4firefox → recommended for checking and updating licenses, accessing online documentation
- Mandatory packages:
- All described operations will have to be performed on the CHARON server and logged in as 'root' (no other user supported).
The 'menu' must be used by one user at a time only - CHARON-AXP and CHARON-VAX installations are supported when installed in
/opt/charon
folder only - Mail service must have been configured. Mail transfer agent can be postfix, sendmail, ...
Conventions
Throughout the document(s) these conventions are followed
Notation | Description |
$ | The dollar sign in interactive examples indicates an operating system prompt for VMS. The dollar sign can also indicate non superuser prompt for UNIX / Linux. |
# | The number sign represents the superuser prompt for UNIX / Linux. |
> | The right angle bracket in interactive examples indicates an operating system prompt for Windows command (cmd.exe). |
| Bold monospace type in interactive examples indicates typed user input. |
| Bold monospace type enclosed by angle brackets indicates command parameters and parameter values. |
| Monospace type in interactive examples, indicates command response output. |
[ ] | In syntax definitions, brackets indicate items that are optional. |
... | In syntax definitions, a horizontal ellipsis indicates that the preceding item can be repeated one or more times. |
| Italic monospace type, in interactive examples, indicates typed context dependent user input. |
The following definitions apply
Term | Description |
---|---|
Host | The system on which the emulator runs, also called the Charon server |
Guest | The operating system running on a Charon instance, for example, Tru64 UNIX, OpenVMS, Solaris, MPE or HP-UX |
Note related to display/edit options
Some menu options will allow you to display or edit files using available editors (if installed) between:
Editor | Interface | Description |
---|---|---|
gedit | Graphical | Windows notepad like |
emacs | Graphical | Windows notepad like, advanced |
nano | Text | Basic text editor |
vi | Text | Advanced users |
vim | Text | Advanced users with more features (colored & highlights) |
gvim | Graphical | Advanced users with more features (colored & highlights) |
Select the one you prefer or refer to 'man pages' for more information on available ones.
Note related to emails
There are 2 kinds of emails:
- Results: some menu options will allow you to send results via email
- Example: license display, log and configuration files.
- The recipient will then be unique
- Alerts: by default, the alert script will send alerts via email plus '
wall
' notifications if enabled. A recipients list can be defined in this case- Wall notification can be enabled/disabled from the menu
- The alert script can be customized. You can for example use command lines linked to your monitoring software and disable emails.
Do not use Stromasys email address to send results directly, for example to support@stromasys.com. The sender will be unknown to us, it is then recommended to send results to yourself first and to forward us the email you received.
Both use 'sendmail
' command to send emails. Mail transfer agent can be postfix, sendmail, ...