Page Comparison

Anchor

	TopRunningPage
	TopRunningPage

...

Use the following symbolic link to run different models of CHARON-VAX:

MicroVAX 3900

Link name	Emulator to run
mv3k6	MicroVAX 3600
mv3k9

mv3k196	MicroVAX 3100 Model 96
mv3k198	MicroVAX 3100 Model 98
mv3k6	MicroVAX 3600
mv3k9	MicroVAX 3900
mvii	MicroVAX II
vs4k90	VAXStation 4000 Model 90
vx3k6	VAXserver 3600
vx3k6_128	VAXserver 3600 (128Mb of RAM is available)
vx3k6_512	VAXserver 3600 (512Mb of RAM is available)
vx3k9	VAXserver 3900
vx3k9_128	VAXserver 3900 (128Mb of RAM is available)
vx3k9_512	VAXserver 3900 (512Mb of RAM is available)
vx4k106	VAX 4000 Model 106
vx4k108	VAX 4000 Model 108
vx4k700	VAX 4000 Model 700
vx4k705	VAX 4000 Model 705
vx6k310	VAX 6310
vx6k610	VAX 6610
vx6k620	VAX 6620
vx6k630	VAX 6630
vx6k640	VAX 6640
vx6k650	VAX 6650
vx6k660	VAX 6660

...

Copy required configuration template from "/opt/charon/cfg/" directory to some local file and set correct privileges to that file to be able to edit it:

...

Installation and start of CHARON-VAX service

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/mv3k6_service` `$ chmod 755 /my_services/mv3k6_service`
Red Hat Linux 7.x and CentOS 7.x	`$ cp /opt/charon/bin/charon.service /usr/lib/systemd/system/mv3k6.service` `$ chmod 755 /usr/lib/systemd/system/mv3k6.service`

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 CentOS 7.x	`ExecStart=/opt/charon/bin/mv3k6 -d /my_services/mv3k6-service.cfg` `WorkingDirectory=/my_services`

"my_mv3k6" is a service name in the example above

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
  class pagebreak
- 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 CentOS 7.x	`# systemctl enable mv3k6.service` `# systemctl start mv3k6.service`

...

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 CentOS 7.x	`# systemctl stop mv3k6`

Please note that before stopping CHARON-VAX service, one must shutdown the operating system running by CHARON-VAX.

...

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 CentOS 7.x	`# systemctl disable mv3k6.service # rm -f /usr/lib/systemd/system/mv3k6.service`

...

Versions Compared

Old Version 5

New Version 6

Key

Installation and start of CHARON-VAX service