From fa1be292894c6c10733ca2e9f0bcdb0cb22340b8 Mon Sep 17 00:00:00 2001
From: gchmurka123 <52824745+gchmurka123@users.noreply.github.com>
Date: Tue, 6 Aug 2024 12:29:00 +0200
Subject: [PATCH] Update znapzendzetup.pod

Fix mysql kill child
https://github.com/oetiker/znapzend/issues/642
---
 doc/znapzendzetup.pod | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/znapzendzetup.pod b/doc/znapzendzetup.pod
index 0719200f..2216b676 100644
--- a/doc/znapzendzetup.pod
+++ b/doc/znapzendzetup.pod
@@ -255,7 +255,7 @@ e.g. for database locking/flushing (pre) and unlocking (post).
 If you deal with a mariadb/mysql database, you can use
 
   pre-snap-command  = /opt/oep/mariadb/bin/mysql -e "set autocommit=0;flush tables with read lock;\\! /bin/sleep 600" &  /usr/bin/echo $! > /tmp/mariadblock.pid ; sleep 10
-  post-snap-command = /usr/bin/kill `/usr/bin/cat /tmp/mariadblock.pid`;/usr/bin/rm /tmp/mariadblock.pid
+  post-snap-command = /usr/bin/pkill -P `/usr/bin/cat /tmp/mariadblock.pid`;/usr/bin/rm /tmp/mariadblock.pid
 
 to make sure that the on-disk data is consistent when snapshotting. The
 lock stays in place only for the duration of the lingering connection