From f9baa95b0f571c936e9406036ead94adc7e098cc Mon Sep 17 00:00:00 2001 From: Alex Young Date: Sat, 14 Jul 2012 17:27:13 +0100 Subject: [PATCH] Raise the log level of a write-request-out-of-range Without this, the error you get is a "Bad magic", when the next read loop tries to read write data as a request. This should be flushed from the socket (although *when* is an open question), but upping the log level at least gives us a more informative output. --- src/client.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/client.c b/src/client.c index 6917a93..48a7a36 100644 --- a/src/client.c +++ b/src/client.c @@ -316,7 +316,7 @@ int client_request_needs_reply( struct client * client, "after an entrust message."); /* check it's not out of range */ if ( request.from+request.len > client->serve->size) { - debug("request read %d+%d out of range", + warn("write request %d+%d out of range", request.from, request.len );