About This Guide
Prev |  | Next

## About This Guide

IRIX Checkpoint and Restart (IRIX CPR) is a facility for saving the state of running processes, and for later resuming execution where it left off. Based on the POSIX 1003.1m standard, this facility was initially implemented in IRIX release 6.4.

This IRIX Checkpoint and Restart Operation Guide describes how to use and administer IRIX CPR, and how to program checkpointing applications.

## Intended Audience

This document is intended for anyone who needs to checkpoint and restart processes, including users, administrators, and application programmers.

## What This Guide Contains

Here is an overview of the material in this book:

- Chapter 1, “Using Checkpoint and Restart”, explains how to checkpoint and restart a process, and how to set CPR control options.

- Chapter 2, “Administering Checkpoint and Restart”, describes how to install and administer CPR, and how to configure state files.

- Chapter 3, “Programming Checkpoint and Restart”, talks about how to program checkpoints into applications.

## Resources for Further Information

The `cpr(1)` man page describes the usage and options of the `cpr` command. The `ckpt_create(3)` man page documents the CPR programming interface; `ckpt_setup(3)`, `ckpt_restart(3)`, `ckpt_stat(3)`, and `ckpt_remove(3)` are links to the same page.

The `atcheckpoint(3C)` man page describes how to set up checkpoint and restart event handlers; `atrestart(3C)` is a link to that page.

## Conventions

The following conventions are used throughout this document:

Purpose | Example
--- | ---
Names of shell commands | The `cpr` command is a command-line interface for CPR.
Command-line options | The `-c` option checkpoints a process, and `-r` restarts it.
System calls and library routines | Processes can checkpoint themselves with `ckpt_create()`.
Filenames and pathnames | Statefile attributes are read from the `$HOME/.cpr` file.
User input (variables in italic) | `cpr -c statefile` ```-p processID`
Exact quotes of computer output | `state10-19: Permission denied.`
Titles of manuals | Refer to IRIX Admin: System Configuration and Operation.
A term defined in the glossary | A DSO (dynamic shared object) is linkable at runtime.

## Reader Comments

If you have comments about the technical accuracy, content, or organization of this document, please tell us. Be sure to include the title and document number of the manual with your comments. (Online, the document number is located in the front matter of the manual. In printed manuals, the document number can be found on the back cover.)

You can contact us in any of the following ways:

- Send e-mail to the following address:

      techpubs@sgi.com

- Use the Feedback option on the Technical Publications Library World Wide Web page:

  http://techpubs.sgi.com

- Contact your customer service representative and ask that an incident be filed in the SGI incident tracking system.

- Send mail to the following address:

  Technical Publications
  SGI
  1600 Amphitheatre Pkwy., M/S 535
  Mountain View, California 94043-1351

- Send a fax to the attention of “Technical Publications” at +1 650 932 0801.

We value your comments and will respond to them promptly.

Prev | Table of Contents | Next
New Features in This Guide |  | Chapter 1. Using Checkpoint and Restart