p2p: Bump time allowing p2p to be used from two to five days.
It's quite unreasonable to expect a site to complete an update of
their entire fleet in just two days.
BUG=chromium:343365
TEST=Unit tests pass.
Change-Id: I974e4573b10acc319661e064ed3f329b6344407f
Reviewed-on: https://chromium-review.googlesource.com/187936
Reviewed-by: Alex Deymo <deymo@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: David Zeuthen <zeuthen@chromium.org>
Tested-by: David Zeuthen <zeuthen@chromium.org>
diff --git a/constants.h b/constants.h
index 12c5941..ae9bde8 100644
--- a/constants.h
+++ b/constants.h
@@ -100,8 +100,8 @@
const int kMaxP2PAttempts = 10;
// Maximum wallclock time we allow attempting to update using p2p for
-// the same update payload - two days.
-const int kMaxP2PAttemptTimeSeconds = 2 * 24 * 60 * 60;
+// the same update payload - five days.
+const int kMaxP2PAttemptTimeSeconds = 5 * 24 * 60 * 60;
// The maximum amount of time to spend waiting for p2p-client(1) to
// return while waiting in line to use the LAN - six hours.