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 log_flush_period
- 1.8 license_key_id
- 1.9 license_id
- 1.10 license_key_lookup_retry
- 1.11 affinity
- 1.12 n_of_cpus
- 1.13 n_of_io_cpus
- 2 File inclusion
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 sections describe all available "session" parameters, their meaning and examples of their usage:
hw_model
Parameter | hw_model |
|---|---|
Type | Text string |
Value | Virtual Alpha system hardware model to be emulated. Use a named template for each model as a starting point for a custom configuration. This would ensure that this parameter is set correctly. Example:
Available models are: AlphaServer_AS400 Refer to this section to find how to set a particular 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). In most cases this is set to the local machine name (TCPIP node identifier for example).
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 highly 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 this CHARON-AXP session is stored. |