f use 1s not 2xping_timer

Author: TheBlueMatt

lightning-background-processor/src/lib.rs

@@ -245,20 +245,20 @@ impl BackgroundProcessor {
 					channel_manager.timer_tick_occurred();
 					last_freshness_call = Instant::now();
 				}
-				if await_time.as_secs() > 2 * PING_TIMER {
+				if await_time > Duration::from_secs(1) {
 					// On various platforms, we may be starved of CPU cycles for several reasons.
 					// E.g. on iOS, if we've been in the background, we will be entirely paused.
 					// Similarly, if we're on a desktop platform and the device has been asleep, we
 					// may not get any cycles.
-					// In any case, if we've been entirely paused for more than double our ping
-					// timer, we should have disconnected all sockets by now (and they're probably
-					// dead anyway).
+					// We detect this by checking if our max-100ms-sleep, above, ran longer than a
+					// full second, at which point we assume sockets may have been killed (they
+					// appear to be at least on some platforms, even if it has only been a second).
 					// Note that we have to take care to not get here just because user event
 					// processing was slow at the top of the loop. For example, the sample client
 					// may call Bitcoin Core RPCs during event handling, which very often takes
 					// more than a handful of seconds to complete, and shouldn't disconnect all our
 					// peers.
-					log_trace!(logger, "Awoke after more than double our ping timer, disconnecting peers.");
+					log_trace!(logger, "100ms sleep took more than a second, disconnecting peers.");
 					peer_manager.disconnect_all_peers();
 					last_ping_call = Instant::now();
 				} else if last_ping_call.elapsed().as_secs() > PING_TIMER {