...
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.
Please note: each instance of Charon-PAR 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:
...
- 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/charon-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 (/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-reloadto 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.
...
Sample service file
Starting the service
Service status
<lines removed> |
...
- Shut down the guest operating system if running.
- Stop the service:
# systemctl stop<guest-name> - Disable the service:
# systemctl disable<guest-name>
...
| Include Page | ||||
|---|---|---|---|---|
|