Changes between Version 11 and Version 12 of ALOELinuxGuide
- Timestamp:
- 03/08/10 15:40:32 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ALOELinuxGuide
v11 v12 38 38 runph is configured with a platform configuration file. However, shell arguments can be used to override some options. The command accepts the following arguments: 39 39 {{{ 40 runph -r [repository_path] -c [platform_cfg_file] -i [xitf_cfg_file] [--daemon]|[--no-daemon] [- o output_file]40 runph -r [repository_path] -c [platform_cfg_file] -i [xitf_cfg_file] [--daemon]|[--no-daemon] [--debug] [-o output_file] 41 41 }}} 42 42 Where: … … 46 46 * ''--daemon'': Run PHAL in background. ''Default'': Foreground. 47 47 * ''--no-daemon'': Run PHAL in foreground. 48 * ''--debug'': Run in debug mode. Do not kill objects at real time failures. 48 49 * ''-o [output_file]'': File to redirect standard output when running as background. ''Default'': output.log 49 50 … … 55 56 ALOE Linux launcher admits two configuration files as arguments which modify certain Platform parameters. In this section we describe how to configure such parameters and what implications do they have: 56 57 57 '''Platform Configuration File''': This file has one mandatory section, ''[cpu_info]'', and N optional sections, ''[daemon]''. The second selects which daemons (and their path)will be launched by runph. You can add or remove them according to which daemons you need in your platform. By default, any platform should run the following daemons:58 '''Platform Configuration File''': This file configures processor options and selects which daemons will be launched by runph. You can add or remove them according to which daemons you need in your platform. By default, any platform should run the following daemons: 58 59 * frontend 59 60 * swload … … 69 70 * sync_master 70 71 71 A single-processor configuration should launch all the daemons except '''sync''' and '''sync_master''' (synchronization is not needed). See MultiProcessorGuide to learn how to work with multi-processors. 72 73 In the CPU section, you can specify some default ALOE configuration parameters. '''Note''': This parameters are overridden by the ones passed as arguments to the ALOE Launcher.72 A single-processor configuration should launch all the daemons except '''sync''' and '''sync_master''' (synchronization is not needed). See MultiProcessorGuide to learn how to work with multi-processors. In the Platform Configuration File, you will find typical configuration sets. 73 74 Some of the parameters can be overriden by arguments in the runph command. The following parameters are available in the Platform Configuration File, also documented in the file: 74 75 * ''name'': The name of the processor. 75 76 * ''mips'': Capacity in MIPS of your computer. … … 79 80 * ''output_file'': File to redirect standard output. 80 81 * ''work_path'': Path to the repository directory 81 82 * ''printbt_atexit'': Print backtrace at object's real time fault 83 * ''printbt_atexit'': Print backtrace at object's exit (overrides atrtfault) 84 * ''itfs_delay'': Object Interfaces default delay. Typical values are: [0,1,2] 85 * ''debug_mode'': Disable real time monitoring (Debug mode) 86 82 87 '''External Interfaces Configuration File''': This files has one section for each external TCP interface of your platform. Before creating a network of ALOE platforms, you should be very familiar with the ALOE Environment concepts as it compromises selecting which daemons will run every platform, which depends on your network architecture. The format of the file is a set of sections (''[xitf]'') with the following mandatory fields: 83 88 * ''id'': Identification of the interface (hexadecimal 16-bit integer). Not any value is accepted as it is used by daemons to discover the purpose of the interface. It must be one of the following:
