1KENTER(2) LAM LOCAL LIBRARY KENTER(2)
2
3
4
6 kenter - Enter process into LAM session.
7
9 int kenter (char *name, int priority);
10
12 subroutine KENTR (name, priority, ierr)
13 character name*(*)
14 integer priority, ierr
15
17 kenter() is the first function a LAM process must call to subsequently
18 use LAM services. By calling underlying functions, kenter() accom‐
19 plishes three important tasks. It initializes all relevant LAM data
20 structures, particularly those for communication with the LAM daemon
21 (see kinit(2)). It registers with the local LAM daemon and sets the
22 message synchronizing priority (see kattach(2)). It also establishes a
23 readable name by which the process can be remotely monitored and con‐
24 trolled (see lpattach(2)).
25
26 The name argument should be the name of the program (argv[0] is recom‐
27 mended) and becomes a convenient recognition string in the output of
28 the state(1) command. It is not used for any type of synchronization.
29
30 Process Scheduling
31 LAM processes are scheduled by the host operating system. The priority
32 argument determines which process will be synchronized first when many
33 are blocked on the same message event and type (see ksend(2)). The
34 highest priority process is always favoured.
35
36 The LAM daemon works like a server. By not replying to a message pass‐
37 ing request, it can effectively block a process from running. The dae‐
38 mon will also attempt to preempt a running process when delivering a
39 LAM signal (see kdoom(2)).
40
42 ENOKERNEL LAM is not running on the local node.
43
44 ENOKDESCRIPTORS The LAM daemon ran out of process descriptors.
45
47 kinit(2), kattach(2), lpattach(2)
48
49
50
51LAM 7.1.2 March, 2006 KENTER(2)