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
NSR checklayout and backup expiration #653
Comments
@tomglx Indeed that makes sense. How would you include this test? You are always welcome to prepare a pull request...thx |
Well, I'm proposing two possible solutions. Even if I would knew enough about git to prepare a pull request, I also would have to know enough |
I guess a script could be created to do this job, e.g. under
However, the content of the script is for me a bit difficult as I have no mean to test whatsoever. |
Here is a draft for such a script. I'm not sure why the content of the EXIT_CODE variable is ignored.
|
@tomglx is the output of
|
@gdha I've included set -xv in the script. Here's the output. Although EXIT_CODE=1, rear -v checklayout finds no difference.
|
@tomglx please move your script from layout/save/NSR/default to layout/compare/NSR/default |
@gdha it wasn't the location. My fault. I didn't expected that the message "Disk layout is identical" wouldn't be printed if my test fails.
|
…tion of a fresh ISO image via rear. See issue #653
rear checklayout detects if the prepared iso image is obsolete. But it doesn't check if all of the available
NSR backups have expired. So how does one prevent this from happening?
I would prefer that checklayout detects this and so a new mkrescue and backup would be done.
By the standard cron job. What could be the correct way to integrate this in the checklayout workflow?
The text was updated successfully, but these errors were encountered: