Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: info box updated with related versions

Anchor
TopRunningPage
TopRunningPage

...

  1. 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/mv3k6_service
    $ chmod 755 /my_services/mv3k6_service

    Red Hat Linux 7.x and Fedora Core

    $ cp /opt/charon/bin/charon.service /usr/lib/systemd/system/mv3k6.service
    $ chmod 755 /usr/lib/systemd/system/mv3k6.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/mv3k6"
    prog="my_mv3k6"
    config="/my_services/mv3k6-service.cfg"

    Red Hat Linux 7.x and Fedora Core

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

              

  3. Create and edit configuration file ( "/my_services/mv3k6-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

      Div
      classpagebreak


    • 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="/my_services/my_mv3k6.log"
      set toy container="/my_services/my_mv3k6.dat"

      load RQDX3/RQDX3 DUA
      set DUA container[0]="/my_services/mv3k6_daemon_boot_disk.vdisk"
      ...

    • Make sure the same physical devices are not used by other CHARON-VAX daemon, same for the OPA0 console port number.

Once configuration file is ready issue the following commands (the specifics belongs to the examples above) to install and start CHARON-VAX as daemon:

Red Hat Linux 6.x

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

Red Hat Linux 7.x and Fedora Core

# systemctl enable mv3k6.service
# systemctl start mv3k6.service

Info
titleRed Hat Linux 7.x and Fedora Core

If you update the /usr/lib/systemd/system/<my virtual machine>.service file, the following command must be executed in order to take changes into account:

# systemctl daemon-reload
Warning

Note that a certain delay may appear in finding network license by Sentinel Run-time on CHARON-VAX host system startup. So if CHARON-VAX service is starting automatically on host system startup 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-VAX will do 5 more attempts waiting 60 seconds between them.

See General Settings section for more details.

...

To stop CHARON-VAX daemon use the following command, for example:

Red Hat Linux 6.x

# service mv3k6_service stop

Red Hat Linux 7.x and Fedora Core

# systemctl stop mv3k6

...

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

Red Hat Linux 6.x

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

Red Hat Linux 7.x and Fedora Core

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

...