-
Notifications
You must be signed in to change notification settings - Fork 260
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
Feature request: support backup_exec scripts with context #170
Labels
Comments
@roaima For integration I would rather see this being configurable to prevent inadvertently leaking information: either on/off switch for the feature or ignore/unignore patterns for the options. I'll have a look into that. |
Sure. I'll see if I can work out how to do that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been using
backup_exec
entries for a while on systems here to drive anrsync
script that understands how to copy only files that been modified in the last 3 years.Unfortunately for my use case,
backup_exec
scripts are run in$HOME
rather than in thesnapshot_root
, which means I have to pass a load of extra parameters to my script that replicate information already provided torsnapshot
.I would like to offer a small patch that exports all the simple configuration variables as environment variables ready for such a script to reference. (I considered patching the change directory requirement so that it was specific to the
preexec
andpostexec
commands but decided against that because that might break existing scripts.)Amongst others, the following environment variables are declared for scripts
rsnapshot.diff.txt
The text was updated successfully, but these errors were encountered: