General Settings
Table of Contents
- 1 Session
- 1.1 hw_model
- 1.2 configuration_name
- 1.3 log
- 1.4 log_method
- 1.5 log_file_size
- 1.6 log_rotation_period
- 1.7 license_key_id
- 1.8 license_key_lookup_retry
- 1.9 affinity
- 1.10 n_of_cpus
- 1.11 n_of_io_cpus
Session
General settings that control the execution of CHARON-AXP belong to an object called the "session". It is a preloaded object; therefore, only "set" commands apply.
Example:
|
The following table describes all available "session" parameters, their meaning and examples of their usage:
hw_model
Parameter | hw_model | |
|---|---|---|
Type | Text string | |
Value | Virtual HP Alpha system hardware model to be emulated. Use a default configuration template for each particular model as a starting point for a custom configuration. This would ensure that the parameter is set correctly. Example:
Available models are:
Refer to this section to find how to set a particular HP Alpha model supported by CHARON-AXP. |
configuration_name
Parameter | configuration_name | ||
|---|---|---|---|
Type | Text string | ||
Value | Name of the CHARON-AXP instance (it must be unique):
The value of this parameter is used as a prefix to the event log file name. (see below). From the example above, the CHARON-AXP log file will have the following name:
xxxxxxxxx is an increasing decimal number starting from 000000000 to separate log files with the same time of creation (in case the log is being written faster than one log file per second). It is strictly recommended to use the "configuration_name" parameter if more than one CHARON instance runs on the same server. |
log
Parameter | log | ||||
|---|---|---|---|---|---|
Type | Text string | ||||
Value | The log file or directory name is where the log file for each CHARON-AXP execution session is stored. Log specified as a file name It is possible to overwrite the existing log file or to extend it using the "log_method" parameter.
Example:
Log specified as a directory CHARON-AXP automatically creates individual log files for each CHARON-AXP execution session. If the log parameter is omitted, CHARON-AXP creates a log file for each CHARON-AXP execution session in the directory where the emulator was started. In these two cases, the log rotation mode is enabled, meaning a new log file is created each time the virtual machine is started and when the log file size exceeds the one specified (see log_file_size) and/or when the log file is older than a specified number of days (see log_rotation_period).
If the "configuration_name" parameter of the session is specified, the log file name is composed as follows:
If the "configuration_name" parameter is omitted, the log file name will have the following format:
where "
Example:
The execution of the virtual machine will create a log file, named |
The "log_method" parameter is effective only when a single log file is specified, not a directory.