From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 1/3] verify: allow '0' days for reverification
Date: Thu, 27 Jan 2022 15:13:19 +0100 [thread overview]
Message-ID: <20220127141321.1072674-1-d.csapak@proxmox.com> (raw)
and let it mean that we will always reverify
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
pbs-api-types/src/jobs.rs | 4 ++--
src/backup/verify.rs | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/pbs-api-types/src/jobs.rs b/pbs-api-types/src/jobs.rs
index c6664104..0e83da73 100644
--- a/pbs-api-types/src/jobs.rs
+++ b/pbs-api-types/src/jobs.rs
@@ -145,8 +145,8 @@ pub const IGNORE_VERIFIED_BACKUPS_SCHEMA: Schema = BooleanSchema::new(
.schema();
pub const VERIFICATION_OUTDATED_AFTER_SCHEMA: Schema = IntegerSchema::new(
- "Days after that a verification becomes outdated")
- .minimum(1)
+ "Days after that a verification becomes outdated. (0 means always)")
+ .minimum(0)
.schema();
#[api(
diff --git a/src/backup/verify.rs b/src/backup/verify.rs
index e37c63be..e835d625 100644
--- a/src/backup/verify.rs
+++ b/src/backup/verify.rs
@@ -560,7 +560,7 @@ pub fn verify_filter(
let now = proxmox_time::epoch_i64();
let days_since_last_verify = (now - last_verify.upid.starttime) / 86400;
- days_since_last_verify > max_age
+ max_age == 0 || days_since_last_verify > max_age
}
}
}
--
2.30.2
next reply other threads:[~2022-01-27 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 14:13 Dominik Csapak [this message]
2022-01-27 14:13 ` [pbs-devel] [PATCH proxmox-backup 2/3] ui: datastore/Content: improve verification actions Dominik Csapak
2022-01-27 14:33 ` [pbs-devel] applied: " Thomas Lamprecht
2022-01-27 14:13 ` [pbs-devel] [PATCH proxmox-backup 3/3] ui: datastore/Content: add 'Re-Verify after (days)' input to 'Verify All' Dominik Csapak
2022-01-27 14:32 ` [pbs-devel] applied: [PATCH proxmox-backup 1/3] verify: allow '0' days for reverification Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220127141321.1072674-1-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox