1LAM_RTRGET(2)                 LAM REMOTE LIBRARY                 LAM_RTRGET(2)
2
3
4

NAME

6       lam_rtrget,  lam_rtrforget,  lam_rtrfget,  lam_rtrfforget  - Unload LAM
7       trace data.
8

SYNOPSIS

10       int lam_rtrget (int nodeid, int listno, int pid, char **buffer);
11
12       int lam_rtrforget (int nodeid, int listno, int pid, char **buffer);
13
14       int lam_rtrfget (int nodeid, int listno, int pid, int fd);
15
16       int lam_rtrfforget (int nodeid, int listno, int pid, int fd);
17

DESCRIPTION

19       The client function, lam_rtrget(), gets a copy of selected  trace  data
20       held  by a remote trace daemon and stores it in space allocated and as‐
21       signed to the buffer argument.  It does not  obtain  trace  data  still
22       stored  with  traced  processes  and not found in the daemon.  A traced
23       process can be forced to flush its trace data by sending it a  SIGTRACE
24       signal.  See MPIL_Signal(2).
25
26       Trace  data  is  unloaded from the selected node and list (see lam_rtr‐
27       store(2)) that was produced by the selected process ID.  A value of  -1
28       for  listno  and/or  pid  selects  all lists and/or all trace producing
29       clients, respectively.  The combination effectively unloads all  stored
30       trace data from the given node.
31
32       Trace  data is read non-destructively by lam_rtrget() and destructively
33       by lam_rtrforget().  The trace data is stored in  an  allocated  buffer
34       whose address is passed back to the caller through the buffer argument.
35       The caller is responsible for calling free(3) on this pointer.
36
37       Trace data is read into a file, instead  of  an  allocated  buffer,  by
38       lam_rtrfget() and lam_rtrfforget().  The file is given as a descriptor,
39       returned by open(2) and opened for write.
40

SEE ALSO

42       lam_rtrstore(2), MPIL_Signal(2)
43
44
45
46LAM 7.1.2                         March, 2006                    LAM_RTRGET(2)
Impressum