commit 0d503945cb527e275ef6644a234a6876ff61322b
from: Alexander Barton <alex@barton.de>
date: Mon May 25 20:59:00 2020 UTC

Revert "Set the "last data" time to "last ping" time when updating the latter"

This patch completely broke the PING-PONG logic: now ngIRCd never
disconnects any stale peers but keeps sending out PINGs over and over
again ...

The real issue (server disconnects right after connect) will be fixed in
the next commit, but let's revert to the somewhat "half-broken but
'known' state" first ...

This reverts commit 79a917f954bef8089967786bd3597a6e5ff5c336.

commit - bae68eb612ef0d8aa515e03c1479e2a57d243dee
commit + 0d503945cb527e275ef6644a234a6876ff61322b
blob - 4a2d32d6a70bcb270981da9b671acc99c6630df3
blob + 72d38b8621ff559c9c93903989e7c091b018be79
--- src/ngircd/conn-func.c
+++ src/ngircd/conn-func.c
@@ -51,7 +51,7 @@ GLOBAL void
 Conn_UpdatePing(CONN_ID Idx)
 {
 	assert(Idx > NONE);
-	My_Connections[Idx].lastping = My_Connections[Idx].lastdata = time(NULL);
+	My_Connections[Idx].lastping = time(NULL);
 }
 
 /*