Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow multiple mkbackuponly or restoreonly running in parallel #1103

Conversation

jsmeix
Copy link
Member

@jsmeix jsmeix commented Dec 5, 2016

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

@jsmeix jsmeix added the enhancement Adaptions and new features label Dec 5, 2016
@jsmeix jsmeix added this to the Rear v2.00 milestone Dec 5, 2016
@jsmeix jsmeix self-assigned this Dec 5, 2016
@jsmeix
Copy link
Member Author

jsmeix commented Dec 5, 2016

With that changes
"Multiple simultaneous backups and/or restores"
work well for me.

@jsmeix jsmeix merged commit d7b6378 into rear:master Dec 5, 2016
@jsmeix jsmeix deleted the Allow_multiple_mkbackuponly_or_restoreonly_running_in_parallel_issue1102 branch December 5, 2016 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adaptions and new features fixed / solved / done
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant