Repository navigation
zfs: fix the documented cron setup - #642
Open
ahoogerhuis wants to merge 1 commit into
Open
ahoogerhuis wants to merge 1 commit into
ahoogerhuis wants to merge 1 commit into
Conversation
ahoogerhuis
marked this pull request as ready for review
October 12, 2026 21:44
Contributor
Author
|
@VVelox |
The cron line omitted -b, so the cache file held raw JSON where the rest of this script's documentation uses the compressed form. Also run the script once before configuring the extend, or the cache file does not exist until cron first fires, and say which crontab the entry belongs in. Made with help from Claude
ahoogerhuis
force-pushed
the
docs/zfs-cron-compressed
branch
from
October 13, 2026 05:23
4f47423 to
6c8eee2
Compare
ahoogerhuis
changed the title
This file contains hidden or 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
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.
The cron example in #640 omitted -b, so the cache file holds raw JSON where
core's docs have always used the compressed form. Also documents running the
script once before the extend is configured — otherwise the cache file does
not exist until cron first fires — and says which crontab the entry belongs
in.
Developed with Claude's assistance; reviewed, I take responsibility for
correctness.