1CONF(5) LAM FILE FORMATS CONF(5)
2
6 conf - LAM node process schema
7
9 Most LAM/MPI used can disregard this page.
10 A process schema lists the system processes that will constitute the
12 LAM environment on a particular node. LAM developers will find process
13 schemata very useful for debugging and for generating custom systems.
14 Separate default configurations files are normally used for booting
16 either the single-daemon version (conf.lam) or the external-servers
17 version (conf.otb). The single-daemon version is used by default. The
18 external-servers version is typically used by LAM developers when
19 debugging LAM services. The -c option to hboot(1) specifies the file
20 name of a custom process schema. This capability is not available with
21 lamboot(1).
22 Application programs can be booted with the LAM environment by includ‐
24 ing the program name in the process schema.
25
27 The process schema grammar defines three types of statements: comments,
28 processes, and options.
29 Comments begin with # and terminate with a newline.
31 Process statements consist of a filename, command line arguments, and
33 possibly options local to the process. The command line arguments are
34 passed to the process when it is started. The process options are used
35 by the booting tools before starting the process.
36 Filenames may include application programs and any of the system pro‐
38 cesses listed below.
39 bforward bufferd helper, forwards remote messages.
41 bufferd creates, kills, sweeps, and states buffers.
43 dli_inet sends data on network connections.
45 dlo_inet receives data from network connections.
47 echod echoes messages; can be used to test nodes and links.
49 filed serves file access.
51 flatd provides symbolic access to node memory.
53 iod handles stdio data of processes.
55 kenyad controls and monitors processes.
57 kernel coordinates message passing.
59 lamd single-daemon version of all servers excluding ledd and
61 mtvd.
62 ledd controls LEDs.
64 loadd loads executable files onto nodes.
66 mtvd controls a pixel map display.
68 router maintains routing tables.
70 traced collects and transports trace data.
72 Processes are started in the order given in the process schema, and for
74 LAM, the order is important. The kernel must be first.
75 Process options are placed inside braces {} following the command line
77 arguments. Process options consist of a keyword followed by an
78 assigned value in parentheses. Options that are not explicitly given
79 have default settings. Options inside braces in process statements
80 apply only to that process. Options outside process statements apply
81 to all processes that appear later in the process schema, unless
82 locally overridden. All the options are listed below:
83 inet_topo a string of dli_inet or lamd options, global only, default
85 null
86 rtr_topo a string of router options, global only, default null
88 delay waiting time in seconds after process boot, default 0
90 The inet_topo and rtr_topo options can be overridden from the command
92 line of hboot(1) using the -I and -R options respectively.
93
95 Following are example process schemata. The first file is used for an
96 OTB node in LAM.
97 ##
99 ## typical LAM process schemata
100 ##
101 lamd $inet_topo
103 The second file is used by LAM developers to control each server as an
105 independent process, typically during debugging.
106 ##
108 ## external-servers LAM process schemata
109 ##
110 ##
112 ## The kernel is listed first.
113 ##
114 kernel $delay
115 ##
117 ## daemons
118 ##
119 router
120 kenyad
121 dli_inet $inet_topo
122 dlo_inet
123 bufferd
124 bforward
125 loadd
126 echod
127 flatd
128 filed
129 traced
130 iod
131
133 $LAMHOME/etc/lam-conf.lamd
134 default LAM node process schema, where $LAMHOME is the installation
135 directory
136 $LAMHOME/etc/lam-conf.separate
138 example external-servers node process schema used when debugging
139 LAM
140
142 hboot(1)
143LAM 7.1.2 March, 2006 CONF(5)