it works in debug mode, as we're single threaded...
in daemon mode, skipping signals when there's no "next" packet
means that it just doesn't respond
We should fix the "skip signal" code to skip the signal only
if the other end hasn't ACKed our last signal. Because when
it drains the queue, it notices that the last packet wasn't
ACKed, and sends an ACK
* predictions about packet processing time?
*/
rad_assert(worker->their_view_of_my_sequence <= worker->sequence);
-#if ENABLE_SKIPS
+#if 0
if (((worker->sequence - worker->their_view_of_my_sequence) <= 1000) &&
((when - worker->last_read_other < SIGNAL_INTERVAL) ||
((when - worker->last_sent_signal) < SIGNAL_INTERVAL))) {