From 2f11c6fb51d34dde49e3829e7014570098ea7c3c Mon Sep 17 00:00:00 2001 From: Janusz Kaczmarek Date: Wed, 5 Jun 2024 17:27:03 +0000 Subject: [PATCH] Bug 37038: koha-elasticsearch creates a file named 0 After execution of koha-elasticsearch command a file named 0 remains in the current directory. Inside the single parentheses, the character '>' is treated as a file redirection, not as a comparison operator. Test plan: ========== 1. Have a test installation with Elasticsearch. As root, perform: ./debian/scripts/koha-elasticsearch --rebuild kohadev When the command finishes, check the contents of the current directory (ls -ltr | tail). You sould notice a fresh file named '0' 2. Apply the patch. Delete the file named 0. 3. Repeat p. 1. There should be no file named 0 now. --- debian/scripts/koha-elasticsearch | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/scripts/koha-elasticsearch b/debian/scripts/koha-elasticsearch index a5428175ac..24f4970941 100755 --- a/debian/scripts/koha-elasticsearch +++ b/debian/scripts/koha-elasticsearch @@ -90,12 +90,12 @@ run_rebuild_elasticsearch() KOHA_BINDIR=${KOHA_HOME}/misc fi - if [ "${clo_commit_size}" > 0 ]; then + if [ "${clo_commit_size}" \> 0 ]; then commit_size=${clo_commit_size} fi rebuild_opts="--commit ${commit_size}" - if [ "${clo_processes}" > 0 ]; then + if [ "${clo_processes}" \> 0 ]; then processes=${clo_processes} fi rebuild_opts="${rebuild_opts} --processes ${processes}" -- 2.39.2