Report actual max_worker_threads in "sanlock client status -D". This allows detecting the issue when sanlock configuration was updated, but sanlock daemon needs a restart to pick up the new configuration.
Signed-off-by: Nir Soffer nsoffer@redhat.com --- src/cmd.c | 2 ++ 1 file changed, 2 insertions(+)
diff --git a/src/cmd.c b/src/cmd.c index a5fa30f..3137df0 100644 --- a/src/cmd.c +++ b/src/cmd.c @@ -2265,6 +2265,7 @@ static int print_state_daemon(char *str) "max_sectors_kb_ignore=%d " "max_sectors_kb_align=%d " "max_sectors_kb_num=%d " + "max_worker_threads=%d " "write_init_io_timeout=%u " "use_aio=%d " "kill_grace_seconds=%d " @@ -2292,6 +2293,7 @@ static int print_state_daemon(char *str) com.max_sectors_kb_ignore, com.max_sectors_kb_align, com.max_sectors_kb_num, + com.max_worker_threads, com.write_init_io_timeout, main_task.use_aio, kill_grace_seconds,
On neděle 6. prosince 2020 19:19:55 CET Nir Soffer wrote:
Report actual max_worker_threads in "sanlock client status -D". This allows detecting the issue when sanlock configuration was updated, but sanlock daemon needs a restart to pick up the new configuration.
Signed-off-by: Nir Soffer nsoffer@redhat.com
src/cmd.c | 2 ++ 1 file changed, 2 insertions(+)
diff --git a/src/cmd.c b/src/cmd.c index a5fa30f..3137df0 100644 --- a/src/cmd.c +++ b/src/cmd.c @@ -2265,6 +2265,7 @@ static int print_state_daemon(char *str) "max_sectors_kb_ignore=%d " "max_sectors_kb_align=%d " "max_sectors_kb_num=%d "
"max_worker_threads=%d "@@ -2292,6 +2293,7 @@ static int print_state_daemon(char *str) com.max_sectors_kb_ignore, com.max_sectors_kb_align, com.max_sectors_kb_num,
com.max_worker_threads,
+1 Vojta
sanlock-devel@lists.fedorahosted.org
-
Nir Soffer -
Vojtech Juranek