cr_run(1)

cr_run1

Runs a subprocess with checkpoint library loaded.

Usage

cr_run [OPTIONS] COMMAND [ARGS]

Overview

cr_run takes an arbitrary command and runs it with the "LD_PRELOAD" environment variable set so that an appropriate shared library is loaded at program startup. Such a library must be loaded if you wish to take a checkpoint of the process with cr_checkpoint(1).

cr_run assumes that BLCR's libraries (libcr*.so) can be found in the default library search path or via the "LD_LIBRARY_PATH" environment variable.

You do not need to use cr_run if you explicitly link your application with -lcr (you may also need to modify your linker's search path with a -L directive, depending on the library's location), or if libcr.so or a related library is loaded by other libraries you have linked with (such as a checkpoint-ready MPI library), or by your system's parallel job startup script, etc. Check your system documentation for details.

Options

-?,--help

print a usage message and exit.

--version

print version information and exit.

--

ends options processing.

--omit

causes executed process(es) to be omitted (rather than included) in any checkpoint taken.

--run

overrides any occurance of --omit earlier in the options (restoring the default behavior).

Releases

Unchanged in 4 releases since Debian 6.0 (Squeeze).

  1. 6.0–9

Bugs

Because cr_run relies on the "LD_PRELOAD" environment variable, it is ineffective for statically-linked executables, and for setuid/gid programs.

Authors

Jason Duell, Paul Hargrove, and Eric Roman, Lawrence Berkeley National Laboratory.

Reporting bugs

Bug reports may be filed on the web at http://mantis.lbl.gov/bugzilla.

From blcr-util 0.8.5-2.3+b1 in Debian 9 (Stretch). Parsed by carta from the page's man source.