On Mon, Nov 03, 2008 at 11:21:26AM -0500, Cole Robinson wrote:
> Daniel P. Berrange wrote:
> > On Thu, Oct 30, 2008 at 02:06:20PM -0400, Cole Robinson wrote:
> >
> >> The attached patch logs the the argv's passed to
> >> the virExec and virRun functions. There's a bit of
> >> trickery here: sinc
Daniel P. Berrange wrote:
> On Thu, Oct 30, 2008 at 02:06:20PM -0400, Cole Robinson wrote:
>
>> The attached patch logs the the argv's passed to
>> the virExec and virRun functions. There's a bit of
>> trickery here: since virRun is just a wrapper for
>> virExec, we don't want the argv string to
On Thu, Oct 30, 2008 at 02:06:20PM -0400, Cole Robinson wrote:
> The attached patch logs the the argv's passed to
> the virExec and virRun functions. There's a bit of
> trickery here: since virRun is just a wrapper for
> virExec, we don't want the argv string to be logged
> twice.
>
> I addressed
The attached patch logs the the argv's passed to
the virExec and virRun functions. There's a bit of
trickery here: since virRun is just a wrapper for
virExec, we don't want the argv string to be logged
twice.
I addressed this by renaming virExec to __virExec,
and keeping the original function nam
