From b13f94a7f50af9e9a35ba21501265aa6632b0003 Mon Sep 17 00:00:00 2001
From: Donald Buczek <buczek@molgen.mpg.de>
Date: Tue, 26 Apr 2022 09:54:59 +0200
Subject: [PATCH] mxqd: Remove missleading logging

The number shown in the messages doesn't make any sense when we are
running `mxqd --recover-only`, so remove the message.

2022-04-25 19:35:43 +0200 mxqd[122093]: recover: reload 9 running jobs from database
2022-04-25 19:35:43 +0200 mxqd[122093]: job finished (via fspool) : job 38218625 pid 79937 status 0
2022-04-25 19:35:43 +0200 mxqd[122093]: job finished (via fspool) : job 38315022 pid 41063 status 0
2022-04-25 19:35:49 +0200 mxqd[122093]: job finished (via fspool) : job 38357611 pid 21477 status 0
2022-04-25 19:35:49 +0200 mxqd[122093]: job finished (via fspool) : job 38359832 pid 52872 status 0
2022-04-25 19:35:49 +0200 mxqd[122093]: recover: processed 12008 finished jobs from fspool
---
 mxqd.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/mxqd.c b/mxqd.c
index 68d599fe..f8e99efa 100644
--- a/mxqd.c
+++ b/mxqd.c
@@ -2442,8 +2442,9 @@ static int recover_from_previous_crash(struct mxq_server *server)
         mx_log_err("recover: server_fspool_scan: %m");
         return res;
     }
-    if (res>0)
-        mx_log_info("recover: processed %d finished jobs from fspool",res);
+    /* Do not log slots returned, because this value is missleading with --recover-only as the current
+     * server may have much smaller slots then the previous server started with memory from
+     * mxqdctl-hostconfig */
 
     res=lost_scan(server);
     if (res<0) {