dtc-xen statslogger breaks and dtc-xen leaks memory after a xm start/stop

[Thomas Goirand]

Binary package hint: dtc-xen

We have discovered that when a xm start/stop/shutdown is requested using
the dtc-xen SOAP daemon, dtc-xen tries to trap the stdout/stderr in
order to be able to forward it to the SOAP client that connects to it.
The issue is that after it did so, it didn't release stderr/stdout,
so that they are going into an internal variable of dtc-xen instead.

The result is that, after a xm start/stop/shutdown:
- dtc-xen leaks memory, with a variable that takes the output of
xm list every minutes
- the dataCollector thread that does xm list cannot get the CPU
statistics as it was designed for, because the output is redirected
to a variable.

Upgrading to version 0.5.13 from SID fixes the issue. This change has
been already accepted by the Squeeze release team. Please sync v0.5.13
from SID ASAP.

See bug repport here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598387

The Debian maintainer and upstream author,

Thomas Goirand (zigo)