pvestatd: run at lease 10 cycles

Comment from Stefan: I've seen that it takes up to 10 cycles to have a
constant memory size. I think this is due to the fact that perls garbage
collection is not running every after each cycle.

bin/pvestatd

@@ -384,7 +384,7 @@ for (;;) { # forever
 
 	my $mem = PVE::ProcFSTools::read_memory_usage();
 
-	if (!defined($initial_memory_usage)) {
+	if (!defined($initial_memory_usage) || ($cycle < 10)) {
 	    $initial_memory_usage = $mem->{resident};
 	} else {
 	    my $diff = $mem->{resident} - $initial_memory_usage;

debian/changelog.Debian

+pve-manager (2.2-26) unstable; urgency=low
+
+  *  pvestatd: fix server reload (run at least 10 cycles)
+
+ -- Proxmox Support Team <support@proxmox.com>  Mon, 29 Oct 2012 13:08:20 +0100
+
 pve-manager (2.2-25) unstable; urgency=low
 
   * pvestatd: fix server reload (due to memory leak)

defines.mk

@@ -2,7 +2,7 @@ RELEASE=2.2
 
 VERSION=2.2
 PACKAGE=pve-manager
-PACKAGERELEASE=25
+PACKAGERELEASE=26
 
 BINDIR=${DESTDIR}/usr/bin
 PERLLIBDIR=${DESTDIR}/usr/share/perl5