From 205f0a3be3d7a389309092685e93c4946794a6c3 Mon Sep 17 00:00:00 2001 From: bunnie Date: Sat, 6 Aug 2022 00:35:18 +0800 Subject: [PATCH] increase threshold for retiring closes when not in heavy loopback mode, this occurs more rarely and probably for more legitimate reasons. --- services/net/src/main.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/services/net/src/main.rs b/services/net/src/main.rs index 8a58e925a..d5a557c77 100644 --- a/services/net/src/main.rs +++ b/services/net/src/main.rs @@ -1695,7 +1695,7 @@ fn main() -> ! { // FORCE_CLOSE_COUNT is an arbitrary threshold where we just decide to stop waiting for the other // side to send the final ack: it's long enough that it almost never times out // incorrectly, but short enough that we're not keeping around baggage forever. - const FORCE_CLOSE_COUNT: u32 = 8; + const FORCE_CLOSE_COUNT: u32 = 16; if !socket.is_open() || *count > FORCE_CLOSE_COUNT { if *count > FORCE_CLOSE_COUNT { log::warn!("forced close on {:?}", socket.local_endpoint());