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

@@ -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
 			);