1PROCSCHEMA(5) LAM FILE FORMATS PROCSCHEMA(5)
2
6 procschema - LAM process schema format
7
9 #
10 # comment
11 #
12 <program> [$delay] [$inet_topo] [<arguments>]
13 <program> [$delay] [$inet_topo] [<arguments>]
14 ...
15
17 Most LAM/MPI users can disregard this page.
18 A process schema (once ambiguously called a configuration file) lists
20 the programs that will constitute the LAM environment on a particular
21 node. It drives the operation of hboot(1). LAM system developers will
22 find process schemata very useful for debugging and for generating cus‐
23 tom systems. By convention these files begin with the prefix conf.
24 The default process schema selected by lamboot(1) (conf.lam) contains
26 only one program, the LAM daemon (lamd). A one program process schema
27 makes the whole business of process schemata and hboot(1) rather redun‐
28 dant. LAM can also be run in a de-clustered mode with the daemon
29 reduced to a simple local message-passing server (the "kernel") and
30 several system clients for network message-passing and remote services.
31 This form of LAM is described in the process schema, conf.otb.
32 The syntax is line oriented. Comments begin with # and terminate with
34 a newline.
35 Process lines consist of a filename, command line arguments, and possi‐
37 bly options and substitution variables. The command line arguments are
38 passed to the process when it is started. The process options control
39 how the process is started. Currently supported process options are:
40 $delay After starting the process, pause before starting the
42 next process.
43 Substitution variables are set by the tools that interpret the process
45 schema and are a way of customizing the process at runtime. See
46 hboot(1). Currently supported substitution variables are:
47 $inet_topo typically, command-line arguments for LAM Internet
49 datalink processes
50 $rtr_topo typically, command-line arguments for the LAM network
52 information process
53 The programs found in the LAM de-clustered mode process schema,
55 conf.otb, are listed below.
56 bufferd Creates, kills, sweeps, and states buffers.
58 bforward Forward messages; helper for bufferd.
59 died Monitors for death of user processes.
60 dli_inet UDP/IP incoming connection to other nodes
61 dlo_inet UDP/IP outgoing connection to other nodes
62 echod Echoes messages; can be used to test nodes and links.
63 filed Serves file access.
64 flatd Provides symbolic access to node memory.
65 kenyad Controls and monitors processes.
66 kernel Coordinates local message-passing.
67 loadd Loads executable files onto nodes.
68 router Maintains network information.
69 traced Collects and transports trace data.
70 Processes are started in the order given in the process schema, and for
72 LAM, the order is important. In particular, the kernel must be first.
73
75 The de-clustered debug mode LAM process schema is shown below:
76 ##
78 ## The kernel is listed first.
79 ##
80 kernel $delay
81 ##
83 ## daemons
84 ##
85 router
86 kenyad
87 dli_inet $inet_topo
88 dlo_inet
89 bufferd
90 bforward
91 loadd
92 echod
93 flatd
94 filed
95 traced
96
98 $LAMHOME/etc/lam-conf.lamd default process schema for lam‐
99 boot(1), where $LAMHOME is the
100 installation directory
101 $LAMHOME/etc/lam-conf.separate default process schema for hboot(1)
103
105 lamboot(1), hboot(1)
106LAM 7.1.2 March, 2006 PROCSCHEMA(5)