CDA SC510 Guia do Utilizador Página 10

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
Vista de página 9
IST-033576 D2.1.4
Once done, user can specify values for the following fields of this structure in
order to tailor the checkpoint to his need :
cr_scope: CR_SCOPE_PROC to checkpoint a process, CR_SCOPE_TREE
for a process tree, CR_SCOPE_PGRP for a process group (as defined by
POSIX, which typically means a command pipeline launched by a shell)
and CR_SCOPE_SESS for a session (which typically means a login shell
and all its descendants or a batch job).
cr_target: Pid of the process that we want to checkpoint.
cr_fd: An open file descriptor where the generated checkpoint file will be
written.
cr_signal: Signal that will be sent to the checkpointed process at the end of
the checkpoint.
cr_timeout: Maximum time allocated to process the checkpoint.
vmadump_flags: VMAD_DUMP_EXEC to save executables, VMA_DUMP_PRIVATE
to save private mappings, VMAD_DUMP_SHARED to save shared map-
pings and VMAD_DUMP_ALL to do a full dump. VMAD_DUMP_EXEC
should be used to save the executable in the context file, and VMA_DUMP_PRIVATE
& VMAD_DUMP_SHARED for the libraries.
cr_flags: Unused in this version.
2.4.3 Checkpoint calls and control
Once the cr_checkpoint_args_t is initialized, a call to the following function should
be done to trigger a checkpoint :
i n t c r _ r e q u e s t _ c h e c k p o i n t ( c r _ c h e c k p o i n t _ a r g s _ t a r g s ,
c r _ c h e c k p o i n t _ h a n d l e _ t h a n d l e ) ;
args is here the previous described checkpoint structure option, and handle is
an opaque output argument that is used by the cr_poll_checkpoint function de-
scribed below.
Return value :
0: The checkpoint has been successfully requested.
<0: an error occurred, typical error can be:
XtreemOS–Integrated Project 8/49
Vista de página 9
1 2 ... 5 6 7 8 9 10 11 12 13 14 15 ... 50 51

Comentários a estes Manuais

Sem comentários