
D2.1.4 IST-033576
• EPERM: One or more of the target processes are not checkpointable
by the current user
• EBADF : The destination (args->cr_fd) is not a valid.
• EINVAL: Some field of the args argument is invalid.
• ...
Check errno-base.h for more details.
As the cr_request_checkpoint system call is not a blocking call, a cr_poll_checkpoint
is provided to allow user to check or block for completion.
i n t c r _ p o l l _ c h e c k p o i n t ( c r _ c h e c k p o i n t _ h a n d l e _ t ∗ha n dle ,
s t r u c t t i m e v a l ∗ t i m e o u t ) ;
Return values of this function are the following :
• >0: checkpoint complete
• 0: it’s not done yet and the timeout (if any) has expired
• <0: an error occurred. Returned values are:
• CR_POLL_CHKPT_ERR_PRE: An error was encountered prior to
completion of the poll/wait operation. Most likely errno values in this
case are:
• EINVAL: No checkpoint request associagted with the given han-
dle. This is the EXPECTED value if the caller is included in the
scope of the checkpoint request and is restarting.
• EINTR: Call was interrupted by a signal.
• CR_POLL_CHKPT_ERR_POST: The negative return value CR_POLL_CHKPT_ERR_POST
indicates that the checkpoint request is completed, but has failed. Most
likely errno values in this case are:
• CR_ENOSUPPORT: One or more of the target processes are not
linked (or LD_PRELOADed) with libcr.
• CR_ETEMPFAIL: One or more of the target processes indicated
a temporary inability to perform the requested checkpoint.
• CR_EPERMFAIL: One or more of the target processes indicated
a permanent inability to perform the requested checkpoint.
• ESRCH: All target processes indicated that they should be omit-
ted from the checkpoint.
9/49 XtreemOS–Integrated Project
Comentários a estes Manuais