[RFE] znapzendsetup : support dst_N_enable setting
#634
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@check-spelling-bot Report jimklimov/znapzend: dst-enable-wip1 into -> oetiker/znapzend: 62394b2🔴 Please reviewSee the 📂 files view, the 📜action log, or 📝 job summary for details. Unrecognized words (1318)Some files were automatically ignored 🙈These sample patterns would exclude them: You should consider adding them to: File matching is via Perl regular expressions. To check these files, more of their words need to be in the dictionary than not. You can use To accept these unrecognized words as correct and update file exclusions, you could run the following commands... in a clone of the https://github.com/oetiker/znapzend repository curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/v0.0.22/apply.pl' |
perl - 'https://github.com/oetiker/znapzend/actions/runs/7821897960/attempts/1'Available 📚 dictionaries could cover words not in the 📘 dictionary
Consider adding them (in with:
extra_dictionaries:
cspell:software-terms/dict/softwareTerms.txt
cspell:python/src/python/python-lib.txt
cspell:php/dict/php.txt
cspell:node/dict/node.txt
cspell:r/src/r.txtTo stop checking additional dictionaries, add (in check_extra_dictionaries: ''Warnings (1)See the 📂 files view, the 📜action log, or 📝 job summary for details.
See ℹ️ Event descriptions for more information. |
jimklimov
changed the title
dst_N_enable settingznapzendsetup : support dst_N_enable setting
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Looking through my old branches, found this bit: the codebase (lib, tests) supports a
dst_N_enablesetting if present among ZFS dataset properties for the backup/retention schedule; however there is no "API way" to toggle this right in the new setting (there is a separateznapzendzetup enable-dst <src_dataset> <DST_key>at this time).Being 5 years old, the idea would need brushing up:
src_mbuffer#632/Allow configuringmbufferpath and size separately for each destination (and source) system #630 recently)First and foremost, the question is if it is worth the effort (is useful)? :)