KENTER(2) LAM LOCAL LIBRARY KENTER(2)NAMEkenter - Enter process into LAM session.
C SYNOPSIS
int kenter (char *name, int priority);
FORTRAN SYNOPSIS
subroutine KENTR (name, priority, ierr)
character name*(*)
integer priority, ierr
DESCRIPTIONkenter() is the first function a LAM process must call to subsequently
use LAM services. By calling underlying functions, kenter() accom‐
plishes three important tasks. It initializes all relevant LAM data
structures, particularly those for communication with the LAM daemon
(see kinit(2)). It registers with the local LAM daemon and sets the
message synchronizing priority (see kattach(2)). It also establishes a
readable name by which the process can be remotely monitored and con‐
trolled (see lpattach(2)).
The name argument should be the name of the program (argv[0] is recom‐
mended) and becomes a convenient recognition string in the output of
the state(1) command. It is not used for any type of synchronization.
Process Scheduling
LAM processes are scheduled by the host operating system. The priority
argument determines which process will be synchronized first when many
are blocked on the same message event and type (see ksend(2)). The
highest priority process is always favoured.
The LAM daemon works like a server. By not replying to a message pass‐
ing request, it can effectively block a process from running. The dae‐
mon will also attempt to preempt a running process when delivering a
LAM signal (see kdoom(2)).
ERRORS
ENOKERNEL LAM is not running on the local node.
ENOKDESCRIPTORS The LAM daemon ran out of process descriptors.
SEE ALSOkinit(2), kattach(2), lpattach(2)LAM 7.1.2 March, 2006 KENTER(2)
