Skip to content

Have --catch-up=SESSION add the new hash files to SESSION#5966

Open
magnumripper wants to merge 1 commit intoopenwall:bleeding-jumbofrom
magnumripper:catch-up-add
Open

Have --catch-up=SESSION add the new hash files to SESSION#5966
magnumripper wants to merge 1 commit intoopenwall:bleeding-jumbofrom
magnumripper:catch-up-add

Conversation

@magnumripper
Copy link
Copy Markdown
Member

@magnumripper magnumripper commented Mar 24, 2026

After the --catch-up=SESSION run finished, add its input files to SESSION's recovery file so that SESSION can simply be resumed for continuing with its old files as well as the new ones.

This can be disabled with a new --no-catch-up-add option.

@magnumripper magnumripper requested a review from solardiz March 24, 2026 12:13
@magnumripper magnumripper force-pushed the catch-up-add branch 3 times, most recently from 583cdd4 to f379506 Compare March 24, 2026 16:52
@magnumripper
Copy link
Copy Markdown
Member Author

This is tested in all relevant ways I could think of, such as with --fork and with any combination of single/multiple files.

After the --catch-up=SESSION run caught up, its input files are now
added to SESSION's recovery file so that it can simply be resumed for
continuing with its old files as well as the new ones.

This can be disabled with a new --no-catch-up-add option.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant