...

Charon-PAR can be started as a service manually and automatically then the Charon host system boots. The service can be stopped manually or automatically when the host system shuts down. When starting

Please note: each instance of Charon-PAR as a service automatic boot of the guest operating system may also be required. Please refer to Guest System Autoboot for more information.  must be started in a separate directory because certain files (SSTORAGE.DAT, NVOLATILE.DAT, UA_SSTORAGE.DAT, and console.dat) will always be created in the current working directory of the emulator instance. Starting multiple emulator instances in the same directory will lead to errors due to file locking problems.

Important points to note when when starting and stopping a Charon-PAR service:

• Only start Charon-PAR and the guest system automatically, if the guest system and guest system applications can be brought up in unattended mode.  Before setting up a service for automatic start, review your system to verify it is suitable for this type of configuration.
• Stopping a Charon-PAR service does not include a clean shut-down of the guest operating system. The guest operating system must be shut down cleanly before the Charon-PAR service is stopped because stopping the service is the equivalent of pulling the power plug. Failing to shut down the operating system cleanly can lead to data corruption, data loss, and even an unbootable guest system. Contact Stromasys or your Stromasys VAR if you require additional information.
• Only activate Charon-PAR as a service during system boot once the correct functioning of all guest system services has been tested manually and a procedure for a clean guest system shutdown has been tested and put in place.
• When starting Charon-PAR as a service automatic boot of the guest operating system may also be required. Please refer to Guest System Autoboot for more information.
• When starting Charon-PAR as a services, you have to manually start the terminal emulator to connect to the console serial port (e.g., PuTTY).

Configuring a systemd Service

...

• Ensure that all paths in your Charon-PAR file are absolute paths.
• Test your Charon-PAR configuration manually until satisfied that it is working correctly and your guest operating system services start as expected.
• Copy /opt/charon/bin/hppacharon-par.service to a local file. For example: <guest-name>.service
• Adapt the service file to contain the correct paths to the Charon-PAR executable (hppa/opt/charon/bin/charon-par) and the Charon-PAR configuration file. If you edit the file after it has been copied to the systemd directory, use systemctl daemon-reload to activate the changes.
• Copy the service file to /etc/systemd/system.
• Test a manual start of the service:
  # systemctl start <guest-name>
• Check the status of the service:
  # systemctl status <guest-name>
• Shut down the guest operating system if running.
• Test a manual stop of the service:
  # systemctl stop <guest-name>
• If everything worked as expected, enable the service for automatic startup:
  # systemctl enable <guest-name>

Please note: The console log output of a service is redirected to journalctl.

The following example shows the content of a service file, starting  the service, and checking the status. The par64> console is reachable on port 5555:

Stopping and Disabling a systemd Service

...