Anchor | ||||
---|---|---|---|---|
|
...
Copy the sample script "/opt/charon/bin/charon" ( "/opt/charon/bin/charon.service" for Fedora Core Linux ) to your home directory (Red Hat Linux) or to "/usr/lib/systemd/system/" directory (Fedora Core), for example:
Red Hat Linux 6.x $ cp /opt/charon/bin/charon /my_services/es40_service
$ chmod 755 /my_services/es40_service
Red Hat Linux 7.x and Fedora Core $ cp /opt/charon/bin/charon.service /usr/lib/systemd/system/es40.service
$ chmod 755 /usr/lib/systemd/system/es40.service
Edit the renamed file to replace sample values of the following parameters, for example:
Red Hat Linux 6.x exec="/opt/charon/bin/es40"
prog="my_es40"
config="/my_services/es40-service.cfg"
Red Hat Linux 7.x and Fedora Core ExecStart=/opt/charon/bin/es40 -d /my_services/es40-service.cfg
WorkingDirectory=/my_services
"my_es40" is a service name in the example above
- Create and edit the configuration file ( "/my_services/es40-service.cfg" in the examples above ) the way it was described before and make sure that the following pre-requisites are met:
OPA0 must be configured as virtual port or physical console, not as operator console, for example:
load virtual_serial_line OPA0 port=10003
#load operator_console OPA0Use only absolute paths to log, toy clock, nvram files and all the other data such as disk images etc. The names of the references files must be unique too, for example
...
set session log="/CharonInstances/1st_es40.log"
set rom container="/CharonInstances/1st_es40.bin"
set toy container="/CharonInstances/1st_es40.dat"set PKA container[0]="/CharonInstances/1st_es40_boot_disk.vdisk"
...
- Make sure the same physical devices are not used by other CHARON-AXP daemons, same for the OPA0 console port number.
...
Once the configuration file is ready run the following commands (from the examples above) to install and start CHARON-AXP as daemon:
Red Hat Linux 6.x |
|
---|---|
Red Hat Linux 7.x and Fedora Core |
|
Info | ||
---|---|---|
| ||
If you update the
|
Warning | ||
---|---|---|
Note that a certain delay may appear in finding network license by Sentinel Run-time on CHARON-AXP host system startup. So if the CHARON-AXP service is starting automatically on a host system, it may report "License not found" error and exit. This problem can be avoided by specifying "license_key_lookup_retry" parameter in the following way:
where:
Example:
In this example if the license key is not found during initial scan, CHARON-AXP will do 5 more attempts waiting 60 seconds between them. See General Settings section for more details. |
...
To stop a CHARON-AXP daemon use the following command, for example:
Red Hat Linux 6.x |
|
---|---|
Red Hat Linux 7.x and Fedora Core |
|
...
To remove a CHARON-AXP daemon use the following commands, for example:
Red Hat Linux 6.x |
|
---|---|
Red Hat Linux 7.x and Fedora Core |
|
...