#1101 PR merged: Enhance logging and progress for running in parallel¶

Labels: enhancement, fixed / solved / done

jsmeix opened issue at 2016-12-05 11:08:¶

Added support for a new variable MESSAGE_PREFIX
that is by default empty so that by default nothing changes
but the user can set it e.g. to MESSAGE_PREFIX="PID$$: "
to get the messages of ReaR output functions
prefixed with ${MESSAGE_PREFIX}.

Added support for a new variable PROGRESS_MODE that
can be PROGRESS_MODE="ANSI" (default/fallback behaviour)
or PROGRESS_MODE="plain" which outputs the same messages
as in default 'ANSI' mode but without ANSI escape sequences.

Added support for a new variable PROGRESS_WAIT_SECONDS
that specifies the number of seconds between progress messages
that are aoutput while a longer task (usually backup or restore) runs.
The default/fallback is 1 second to keep the current behaviour.

Setting at least MESSAGE_PREFIX="PID$$: "
and PROGRESS_MODE="plain" is needed to get
still usable (i.e. meaningful) output when multiple
"rear mkbackuponly" or "rear restoreonly" run in parallel.

Optionally setting PROGRESS_WAIT_SECONDS="5"
results much less progress messages but at the same time
it delays continuing after the task (e.g. backup or restore)
had finished by half that time on average up to at most
the whole amount of PROGRESS_WAIT_SECONDS.

jsmeix commented at 2016-12-05 11:13:¶

This should fix
https://github.com/rear/rear/issues/1096

---

[Export of Github issue for rear/rear.]