CDA SC510 Guida Utente Pagina 44

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
Vedere la pagina 43
IST-033576 D2.1.4
The above examples set the PATH, MANPATH and LD_LIBRARY_PATH
variables in your current shell only. It is strongly recommended that you make
these settings permanent, to make these settings affect future sessions or windows.
To do this, you must add the example commands to your shell’s start up files. For a
single user of BLCR, you should add the appropriate set of commands to the shell
startup files in your home directory (.bashrc for bash, .profile for other bourne-
type shells, or .cshrc for csh-type shells). For a system-wide installation, add the
bourne shell commands to /etc/bashrc and /etc/profile and the csh commands to
/etc/cshrc.
B.4 Checkpointing/restarting applications on a single machine
B.4.1 Types of applications supported
BLCR currently supports:
Single threaded applications
Multithreaded applications using either LinuxThreads or NPTL (the old and
new Linux pthreads implementations, respectively)
Process trees, meaning a process and all its "reachable" descendants (ex-
cluding those who’s parent has exited)
Process groups (as defined by POSIX), which typically means a command
pipeline launched by a shell (e.g. cat foo bar | sort)
POSIX sessions, which typically means a login shell and all its descendants
or a batch job
However, certain applications are not supported because they use resources
not restored by BLCR:
Applications which use sockets (regardless of address family). If a check-
point is taken of a process with open sockets, they will not be restored when
the process is restarted. Applications or libraries may register a checkpoint
callback to manage socket connections to re-open them at restart time (this
is how MPI libraries typically work with BLCR), but the core BLCR check-
pointer does not directly support restoring sockets. NEW: This behavior is
a change from releases prior to 0.5.0 which would fail at checkpoint time if
sockets were open.
Applications which use SystemV IPC mechanisms including shared mem-
ory, semaphores and message queues. As with sockets, code that is BLCR-
aware may choose to take its own measures to deal with these resources.
XtreemOS–Integrated Project 42/49
Vedere la pagina 43
1 2 ... 39 40 41 42 43 44 45 46 47 48 49 50 51

Commenti su questo manuale

Nessun commento