Re: [libvirt] [PATCH 3/3]: Read cmd stdout + stderr in virRun

2008-11-03 Thread Daniel P. Berrange
On Thu, Oct 30, 2008 at 02:06:35PM -0400, Cole Robinson wrote: The attached patch is my second cut at reading stdout and stderr of the command virRun kicks off. There is no hard limit to the amount of data we read now, and we use a poll loop to avoid any possible full buffer issues. If

Re: [libvirt] [PATCH 3/3]: Read cmd stdout + stderr in virRun

2008-11-03 Thread Cole Robinson
Daniel P. Berrange wrote: On Thu, Oct 30, 2008 at 02:06:35PM -0400, Cole Robinson wrote: The attached patch is my second cut at reading stdout and stderr of the command virRun kicks off. There is no hard limit to the amount of data we read now, and we use a poll loop to avoid any

[libvirt] [PATCH 3/3]: Read cmd stdout + stderr in virRun

2008-10-30 Thread Cole Robinson
The attached patch is my second cut at reading stdout and stderr of the command virRun kicks off. There is no hard limit to the amount of data we read now, and we use a poll loop to avoid any possible full buffer issues. If stdout or stderr had any content, we DEBUG it, and if the command

Re: [libvirt] [PATCH 3/3]: Read cmd stdout + stderr in virRun

2008-10-30 Thread Jim Meyering
Cole Robinson [EMAIL PROTECTED] wrote: The attached patch is my second cut at reading stdout and stderr of the command virRun kicks off. There is no hard limit to the amount of data we read now, and we use a poll loop to avoid any possible full buffer issues. If stdout or stderr had any