fix bug in fork_worker

This commit is contained in:
Dietmar Maurer 2011-10-11 08:37:32 +02:00
parent b9e47e5738
commit 5bf71a968e
3 changed files with 12 additions and 4 deletions

View File

@ -2,7 +2,7 @@ RELEASE=2.0
VERSION=1.0
PACKAGE=libpve-access-control
PKGREL=1
PKGREL=2
DESTDIR=
PREFIX=/usr

View File

@ -316,8 +316,10 @@ sub get_user {
# read/update list of active workers
# we move all finished tasks to the archive index,
# but keep aktive and most recent task in the active file.
# $nocheck ... consider $new_upid still running (avoid that
# we try to read the reult to early.
sub active_workers {
my ($new_upid) = @_;
my ($new_upid, $nocheck) = @_;
my $lkfn = "/var/log/pve/tasks/.active.lock";
@ -354,7 +356,7 @@ sub active_workers {
$task = PVE::Tools::upid_decode($new_upid);
$task->{upid} = $new_upid;
$thash->{$new_upid} = $task;
&$check_task($task);
&$check_task($task) if !$nocheck;
}
@ -639,7 +641,7 @@ sub fork_worker {
PVE::Cluster::log_msg('info', $user, "starting task $upid");
my $tlist = active_workers($upid);
my $tlist = active_workers($upid, $sync);
PVE::Cluster::broadcast_tasklist($tlist);
my $res = 0;

View File

@ -1,3 +1,9 @@
libpve-access-control (1.0-2) unstable; urgency=low
* fix bug in fork_worker
-- Proxmox Support Team <support@proxmox.com> Tue, 11 Oct 2011 08:37:05 +0200
libpve-access-control (1.0-1) unstable; urgency=low
* allow '-' in permission paths