[checkmk-commits] [tribe29/checkmk] 647481: Rework locking for mkbackup

Branch: refs/heads/1.6.0 Home: https://github.com/tribe29/checkmk Commit: 6474817da049ec6ca886ce02c71a9ac2d636a8d1 https://github.com/tribe29/checkmk/commit/6474817da049ec6ca886ce02c71a9ac2d… Author: Timotheus Bachinger &lt;timotheus.bachinger(a)tribe29.com&gt; Date: 2021-07-12 (Mon, 12 Jul 2021) Changed paths: M bin/mkbackup M cmk/utils/paths.py Log Message: ----------- Rework locking for mkbackup We're using now multiple files for flock: * one lock *per* site, which is backuped / restored * one global lock, in case of an appliance (and mkbackup executed by root) CMK-7706 Change-Id: I9c498b7ff1e45dec5d6f17e1df605c6930d288d1 Commit: 033a154c28426c51c856efd0e31082bd51cddd50 https://github.com/tribe29/checkmk/commit/033a154c28426c51c856efd0e31082bd5… Author: Timotheus Bachinger &lt;timotheus.bachinger(a)tribe29.com&gt; Date: 2021-07-12 (Mon, 12 Jul 2021) Changed paths: A .werks/11810 M omd/omd.spec.in M omd/packages/omd/omdlib/main.py Log Message: ----------- 11810 FIX mkbackup: Fix locking problems On standard site installations, locks during mkbackup are now site specific. This results in multiple sites being able to be backed-up simultaneously. On appliances, a system-wide backup will still lock all sites regarding backup. Details: Werk 11868 tried to fix permission issues during mkbackup of different sites. However directories under <tt>/var/lock/</tt> are volatile and therefore the creation and the setting of the rights on the <tt>mkbackup</tt> folder must be performed on every system restart. Therefore <tt>omd</tt> will now try to ensure that this folder exists and has the correct permissions. Furthermore, the backup directory has been moved to <tt>/run/lock/mkbackup</tt> as this is the standard path for locks according to FHS. CMK-7706 Change-Id: I34f52241c1bb17a300c0c00a621b667db48e30cf Compare: https://github.com/tribe29/checkmk/compare/abde931e6c5a...033a154c2842