1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376
|
.TH kernel 6 "kernel 2.12.3" "Ericsson AB" "ERLANG APPLICATION DEFINITION"
.SH APPLICATION
kernel \- The Kernel Application
.SH DESCRIPTION
.LP
The Kernel application is the first application started\&. It is mandatory in the sense that the minimal system based on Erlang/OTP consists of Kernel and STDLIB\&. The Kernel application contains the following services:
.RS 2
.TP 2
*
application controller, see \fIapplication(3)\fR
.TP 2
*
\fIcode\fR
.TP 2
*
\fIdisk_log\fR
.TP 2
*
\fIdist_ac\fR, distributed application controller
.TP 2
*
\fIerl_boot_server\fR
.TP 2
*
\fIerl_ddll\fR
.TP 2
*
\fIerror_logger\fR
.TP 2
*
\fIfile\fR
.TP 2
*
\fIglobal\fR
.TP 2
*
\fIglobal_group\fR
.TP 2
*
\fIheart\fR
.TP 2
*
\fIinet\fR
.TP 2
*
\fInet_kernel\fR
.TP 2
*
\fIos\fR
.TP 2
*
\fIpg2\fR
.TP 2
*
\fIrpc\fR
.TP 2
*
\fIseq_trace\fR
.TP 2
*
\fIuser\fR
.RE
.SH ERROR LOGGER EVENT HANDLERS
.LP
Two standard error logger event handlers are defined in the Kernel application\&. These are described in error_logger(3)\&.
.SH CONFIGURATION
.LP
The following configuration parameters are defined for the Kernel application\&. See \fIapp(3)\fR for more information about configuration parameters\&.
.RS 2
.TP 4
.B
\fIbrowser_cmd = string() | {M, F, A}\fR:
When pressing the Help button in a tool such as Debugger or TV, the help text (an HTML file \fIFile\fR) is by default displayed in a Netscape browser which is required to be up and running\&. This parameter can be used to change the command for how to display the help text if another browser than Netscape is preferred, or another platform than Unix or Windows is used\&.
.RS 4
.LP
.LP
If set to a string \fICommand\fR, the command \fI"Command File"\fR will be evaluated using \fIos:cmd/1\fR\&.
.LP
.LP
If set to a module-function-args tuple \fI{M, F, A}\fR, the call \fIapply(M, F, [File|A])\fR will be evaluated\&.
.RE
.TP 4
.B
\fIdistributed = [Distrib]\fR:
Specifies which applications are distributed and on which nodes they may execute\&. In this parameter:
.RS 4
.LP
.RS 2
.TP 2
*
\fIDistrib = {App, Nodes} | {App, Time, Nodes}\fR
.TP 2
*
\fIApp = atom()\fR
.TP 2
*
\fITime = integer()>0\fR
.TP 2
*
\fINodes = [node() | {node(), \&.\&.\&., node()}]\fR
.RE
.LP
.LP
The parameter is described in \fIapplication(3)\fR, function \fIload/2\fR\&.
.RE
.TP 4
.B
\fIdist_auto_connect = Value\fR:
Specifies when nodes will be automatically connected\&. If this parameter is not specified, a node is always automatically connected, e\&.g when a message is to be sent to that node\&. \fIValue\fR is one of:
.RS 4
.LP
.RS 2
.TP 4
.B
\fInever\fR:
Connections are never automatically connected, they must be explicitly connected\&. See \fInet_kernel(3)\fR\&.
.TP 4
.B
\fIonce\fR:
Connections will be established automatically, but only once per node\&. If a node goes down, it must thereafter be explicitly connected\&. See \fInet_kernel(3)\fR\&.
.RE
.RE
.TP 4
.B
\fIpermissions = [Perm]\fR:
Specifies the default permission for applications when they are started\&. In this parameter:
.RS 4
.LP
.RS 2
.TP 2
*
\fIPerm = {ApplName, Bool}\fR
.TP 2
*
\fIApplName = atom()\fR
.TP 2
*
\fIBool = boolean()\fR
.RE
.LP
.LP
Permissions are described in \fIapplication(3)\fR, function \fIpermit/2\fR\&.
.RE
.TP 4
.B
\fIerror_logger = Value\fR:
\fIValue\fR is one of:
.RS 4
.LP
.RS 2
.TP 4
.B
\fItty\fR:
Installs the standard event handler which prints error reports to \fIstdio\fR\&. This is the default option\&.
.TP 4
.B
\fI{file, FileName}\fR:
Installs the standard event handler which prints error reports to the file \fIFileName\fR, where \fIFileName\fR is a string\&.
.TP 4
.B
\fIfalse\fR:
No standard event handler is installed, but the initial, primitive event handler is kept, printing raw event messages to tty\&.
.TP 4
.B
\fIsilent\fR:
Error logging is turned off\&.
.RE
.RE
.TP 4
.B
\fIglobal_groups = [GroupTuple]\fR:
Defines global groups, see \fIglobal_group(3)\fR\&.
.RS 4
.LP
.RS 2
.TP 2
*
\fIGroupTuple = {GroupName, [Node]} | {GroupName, PublishType, [Node]}\fR
.TP 2
*
\fIGroupName = atom()\fR
.TP 2
*
\fIPublishType = normal | hidden\fR
.TP 2
*
\fINode = node()\fR
.RE
.RE
.TP 4
.B
\fIinet_default_connect_options = [{Opt, Val}]\fR:
Specifies default options for \fIconnect\fR sockets, see \fIinet(3)\fR\&.
.TP 4
.B
\fIinet_default_listen_options = [{Opt, Val}]\fR:
Specifies default options for \fIlisten\fR (and \fIaccept\fR) sockets, see \fIinet(3)\fR\&.
.TP 4
.B
\fI{inet_dist_use_interface, ip_address()}\fR:
If the host of an Erlang node has several network interfaces, this parameter specifies which one to listen on\&. See \fIinet(3)\fR for the type definition of \fIip_address()\fR\&.
.TP 4
.B
\fI{inet_dist_listen_min, First}\fR:
See below\&.
.TP 4
.B
\fI{inet_dist_listen_max, Last}\fR:
Define the \fIFirst\&.\&.Last\fR port range for the listener socket of a distributed Erlang node\&.
.TP 4
.B
\fIinet_parse_error_log = silent\fR:
If this configuration parameter is set, no \fIerror_logger\fR messages are generated when erroneous lines are found and skipped in the various Inet configuration files\&.
.TP 4
.B
\fIinetrc = Filename\fR:
The name (string) of an Inet user configuration file\&. See ERTS User\&'s Guide, Inet configuration\&.
.TP 4
.B
\fInet_setuptime = SetupTime\fR:
.RS 4
.LP
\fISetupTime\fR must be a positive integer or floating point number, and will be interpreted as the maximally allowed time for each network operation during connection setup to another Erlang node\&. The maximum allowed value is 120; if higher values are given, 120 will be used\&. The default value if the variable is not given, or if the value is incorrect (e\&.g\&. not a number), is 7 seconds\&.
.LP
.LP
Note that this value does not limit the total connection setup time, but rather each individual network operation during the connection setup and handshake\&.
.RE
.TP 4
.B
\fInet_ticktime = TickTime\fR:
.RS 4
.LP
Specifies the \fInet_kernel\fR tick time\&. \fITickTime\fR is given in seconds\&. Once every \fITickTime/4\fR second, all connected nodes are ticked (if anything else has been written to a node) and if nothing has been received from another node within the last four (4) tick times that node is considered to be down\&. This ensures that nodes which are not responding, for reasons such as hardware errors, are considered to be down\&.
.LP
.LP
The time \fIT\fR, in which a node that is not responding is detected, is calculated as: \fIMinT < T < MaxT\fR where:
.LP
.nf
MinT = TickTime - TickTime / 4
MaxT = TickTime + TickTime / 4
.fi
.LP
.LP
\fITickTime\fR is by default 60 (seconds)\&. Thus, \fI45 < T < 75\fR seconds\&.
.LP
.LP
\fINote:\fR All communicating nodes should have the same \fITickTime\fR value specified\&.
.LP
.LP
\fINote:\fR Normally, a terminating node is detected immediately\&.
.RE
.TP 4
.B
\fIsync_nodes_mandatory = [NodeName]\fR:
Specifies which other nodes \fImust\fR be alive in order for this node to start properly\&. If some node in the list does not start within the specified time, this node will not start either\&. If this parameter is undefined, it defaults to []\&.
.TP 4
.B
\fIsync_nodes_optional = [NodeName]\fR:
Specifies which other nodes \fIcan\fR be alive in order for this node to start properly\&. If some node in this list does not start within the specified time, this node starts anyway\&. If this parameter is undefined, it defaults to the empty list\&.
.TP 4
.B
\fIsync_nodes_timeout = integer() | infinity\fR:
Specifies the amount of time (in milliseconds) this node will wait for the mandatory and optional nodes to start\&. If this parameter is undefined, no node synchronization is performed\&. This option also makes sure that \fIglobal\fR is synchronized\&.
.TP 4
.B
\fIstart_dist_ac = true | false\fR:
Starts the \fIdist_ac\fR server if the parameter is \fItrue\fR\&. This parameter should be set to \fItrue\fR for systems that use distributed applications\&.
.RS 4
.LP
.LP
The default value is \fIfalse\fR\&. If this parameter is undefined, the server is started if the parameter \fIdistributed\fR is set\&.
.RE
.TP 4
.B
\fIstart_boot_server = true | false\fR:
Starts the \fIboot_server\fR if the parameter is \fItrue\fR (see \fIerl_boot_server(3)\fR)\&. This parameter should be set to \fItrue\fR in an embedded system which uses this service\&.
.RS 4
.LP
.LP
The default value is \fIfalse\fR\&.
.RE
.TP 4
.B
\fIboot_server_slaves = [SlaveIP]\fR:
If the \fIstart_boot_server\fR configuration parameter is \fItrue\fR, this parameter can be used to initialize \fIboot_server\fR with a list of slave IP addresses\&. \fISlaveIP = string() | atom | {integer(), integer(), integer(), integer()}\fR
.RS 4
.LP
.LP
where \fI0 <= integer() <=255\fR\&.
.LP
.LP
Examples of \fISlaveIP\fR in atom, string and tuple form are:
.br
\fI\&'150\&.236\&.16\&.70\&', "150, 236, 16, 70", {150, 236, 16, 70}\fR\&.
.LP
.LP
The default value is \fI[]\fR\&.
.RE
.TP 4
.B
\fIstart_disk_log = true | false\fR:
Starts the \fIdisk_log_server\fR if the parameter is \fItrue\fR (see \fIdisk_log(3)\fR)\&. This parameter should be set to true in an embedded system which uses this service\&.
.RS 4
.LP
.LP
The default value is \fIfalse\fR\&.
.RE
.TP 4
.B
\fIstart_pg2 = true | false\fR:
Starts the \fIpg2\fR server (see \fIpg2(3)\fR) if the parameter is \fItrue\fR\&. This parameter should be set to \fItrue\fR in an embedded system which uses this service\&.
.RS 4
.LP
.LP
The default value is \fIfalse\fR\&.
.RE
.TP 4
.B
\fIstart_timer = true | false\fR:
Starts the \fItimer_server\fR if the parameter is \fItrue\fR (see \fItimer(3)\fR)\&. This parameter should be set to \fItrue\fR in an embedded system which uses this service\&.
.RS 4
.LP
.LP
The default value is \fIfalse\fR\&.
.RE
.TP 4
.B
\fIshutdown_func = {Mod, Func}\fR:
Where:
.RS 4
.LP
.RS 2
.TP 2
*
\fIMod = atom()\fR
.TP 2
*
\fIFunc = atom()\fR
.RE
.LP
.LP
Sets a function that \fIapplication_controller\fR calls when it starts to terminate\&. The function is called as: \fIMod:Func(Reason)\fR, where \fIReason\fR is the terminate reason for \fIapplication_controller\fR, and it must return as soon as possible for \fIapplication_controller\fR to terminate properly\&.
.RE
.RE
.SH SEE ALSO
.LP
app(4), application(3), code(3), disk_log(3), erl_boot_server(3), erl_ddll(3), error_logger(3), file(3), global(3), global_group(3), heart(3), inet(3), net_kernel(3), os(3), pg2(3), rpc(3), seq_trace(3), user(3)
|