Fabian Ebner 5bf0bc3569 fix #2821: only abort if there really is a waiting/syncing job ... by remembering the process via PID+start time+boot ID and checking for that information in the new instance. If the old instance can't be found, the new one will continue and register itself in the state. After updating the pve-zsync package, if there is a waiting instance running the old version, one more might be created, because there is no instance_id yet. But the new instance will set the instance_id, which any later instance will see. More importantly, if the state is wrongly 'waiting' or 'syncing', i.e. because an instance was terminated before finishing, we don't abort anymore and recover from the wrong state, thus fixing the bug. Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>		2020-12-18 17:41:18 +01:00
debian	bump version to 2.0-4	2020-11-26 05:57:22 +01:00
Makefile	buildsys: switch upload dist over to buster	2019-05-23 18:18:32 +02:00
pve-zsync	fix #2821: only abort if there really is a waiting/syncing job	2020-12-18 17:41:18 +01:00