Commit c164a0f7 authored by Kevin Harms's avatar Kevin Harms

Minor fixes to documentation

git-svn-id: https://svn.mcs.anl.gov/repos/darshan/trunk@534 3b7491f3-a168-0410-bf4b-c445ed680a29
parent 368c9594
......@@ -10,7 +10,7 @@ system where you intend to collect I/O characterization information.
Darshan instruments applications via either compile time wrappers for static
executables or dynamic library preloading for dynamic executables. An
application that has been instrumented with Darshan will produce a single
log file each time is executed. This log summarizes the I/O access patterns
log file each time it is executed. This log summarizes the I/O access patterns
used by the application.
The darshan-runtime instrumentation only instruments MPI applications (the
......
......@@ -52,7 +52,7 @@ application will likely be found in a centralized directory, with the path
and log file name in the following format:
----
<YEAR>/<MONTH>/<DAY>/<USERNAME>_<BINARY_NAME>_<JOB_ID>_<DATE>.darshan.gz
<YEAR>/<MONTH>/<DAY>/<USERNAME>_<BINARY_NAME>_<JOB_ID>_<DATE>_<UNIQUE_ID>_<TIMING>.darshan.gz
----
This is a binary format file that summarizes I/O activity. As of version
......@@ -347,7 +347,7 @@ differ
* darshan-analyzer: walks an entire directory tree of Darshan log files and
produces a summary of the types of access methods used in those log files
* darshan-logutils*: this is a library rather than an executable, but it
provides a C inteface for opening and parsing Darshan log files. This is
provides a C interface for opening and parsing Darshan log files. This is
the recommended method for writing custom utilities, as darshan-logutils
provides a relatively stable interface across different versions of Darshan
and different log formats.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment