# -*- text -*-
#
# Copyright (c) 2026      Nanook Consulting  All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
# This is the US/English help file for PRRTE's filem:raw component.
#
[preload-collision]
A preloaded file cannot be placed in the working directory of the
processes that are to use it: something else of that name is already
there, and its contents are not what was to be staged.

   File:              %s
   Working directory: %s
   Node:              %s

PRRTE will not overwrite a file it did not put there, so the job has been
aborted.
#
[preload-bad-path]
A file requested for preloading cannot be delivered under the name it was
given:

   File: %s

A preloaded file is always placed inside the working directory of the
processes that are to use it, so the name it is delivered under must be a
plain relative path within that directory. A name containing a ".."
component would place the file outside it - somewhere the application
never asked for, on every node of the DVM - so the job has been aborted.
Name the file by a path relative to the directory it should appear in, or
by an absolute path (in which case it is delivered under its basename).
#
[preload-name-clash]
Two different files requested for preloading would be delivered under the
same name in the working directory of the processes that are to use them:

   First:  %s
   Second: %s
   Name:   %s

Only one of them could be delivered, so the job has been aborted rather
than silently choosing between them. Note that a file named by an absolute
path is delivered under its basename; name the files by paths relative to a
common directory, or rename one of them, and try again.
#
[preload-not-staged]
A file requested for preloading never arrived on the node that was to run
the processes using it:

   File: %s
   Node: %s

The job has been aborted rather than started in a working directory that
does not contain a file it was promised. This is an internal
inconsistency - the job should not have been launched until every daemon
acknowledged every file - so please report it, along with the output of
"prte_info --all", at https://github.com/openpmix/prrte/issues.
