Allow multiple mkbackuponly or restoreonly running in parallel #1103
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New SIMULTANEOUS_RUNNABLE_WORKFLOWS variable
lists those workflows that are allowed to run simultaneously
but cannot use LOGFILE.lockless as the LOCKLESS_WORKFLOWS.
Instead the SIMULTANEOUS_RUNNABLE_WORKFLOWS
get a LOGFILE with PID because simultaneously runnable
workflows require unique logfile names, see
#1102
Additional enhancements and fixes in usr/sbin/rear:
CONFIG_APPEND_FILES that are not in CONFIG_DIR
get added to COPY_AS_IS to get them copied into the
recovery system.
Moved progress subsystem enablement
(i.e. source $SHARE_DIR/lib/progresssubsystem.nosh)
and enablement of debug output of the progress pipe
after the user config files had been read, because
otherwise a PROGRESS_MODE setting in a
user config file is not used when defining the
progress functions inprogresssubsystem.nosh