Versions Compared

Old Version 6

changes.mady.by.user Kirill Nikolaev (Unlicensed)

Saved on

compared with

New Version 7

changes.mady.by.user Bruno Miretti (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minor update

Anchor
TopRunningPage
TopRunningPage

...

  1. Copy the sample script "/opt/charon/bin/charon.service" ( "/opt/charon/bin/charon" for Red Hat  Linux 6.x) to "/usr/lib/systemd/system/" directory (or to your home directory (Red Hat Linux 6.x)), 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 CentOS 7.x

    $ cp /opt/charon/bin/charon.service /usr/lib/systemd/system/es40.service
    $ chmod 755 /usr/lib/systemd/system/es40.service

  2. 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 CentOS 7.x

    ExecStart=/opt/charon/bin/es40 -d /my_services/es40-service.cfg
    WorkingDirectory=/my_services

    (warning) "my_es40" is a service name in the example above

              

  3. 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 OPA0

    • Use 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

# ln -sf /my_services/es40_service /etc/init.d/es40_service
# chkconfig es40_service on
# service es40_service start

Red Hat Linux 7.x and CentOS 7.x

# systemctl enable es40.service
# systemctl start es40.service

...

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:

set session license_key_lookup_retry = "N [, T]"

where:

  • N - Number of retries looking for license key (or keys)
  • T - Time between retries in seconds. If not specified 60 seconds is used

Example:

set session license_key_lookup_retry = 5

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

# service es40_service stop

Red Hat Linux 7.x and CentOS 7.x

# systemctl stop es40

(warning) Please note that before stopping CHARON-AXP service, one must shutdown the operating system running in CHARON-AXP. 

...

To remove a CHARON-AXP daemon use the following commands, for example:

Red Hat Linux 6.x

# chkconfig es40_service off
# chkconfig --del es40_service
# rm -f /etc/init.d/es40_service

Red Hat Linux 7.x and CentOS 7.x

# systemctl disable es40.service
# rm -f /usr/lib/systemd/system/es40.service 

...