Cole Robinson wrote:
> Daniel P. Berrange wrote:
>> On Mon, Feb 16, 2009 at 06:42:11PM -0500, Cole Robinson wrote:
>>> For some reason there are two VMDef members being used to keep track of
>>> monitor event handles: monitor_watch and monitorWatch. Remove the latter.
>> Can you remove the 'monitor
On Fri, Feb 27, 2009 at 10:38:45AM -0500, Cole Robinson wrote:
> Daniel P. Berrange wrote:
> > On Mon, Feb 16, 2009 at 06:42:11PM -0500, Cole Robinson wrote:
> >> For some reason there are two VMDef members being used to keep track of
> >> monitor event handles: monitor_watch and monitorWatch. Remo
Cole Robinson wrote:
> Daniel P. Berrange wrote:
>> On Mon, Feb 16, 2009 at 06:42:11PM -0500, Cole Robinson wrote:
>>> For some reason there are two VMDef members being used to keep track of
>>> monitor event handles: monitor_watch and monitorWatch. Remove the latter.
>>
>> Can you remove the 'moni
Daniel P. Berrange wrote:
> On Mon, Feb 16, 2009 at 06:42:11PM -0500, Cole Robinson wrote:
>> For some reason there are two VMDef members being used to keep track of
>> monitor event handles: monitor_watch and monitorWatch. Remove the latter.
>
> Can you remove the 'monitor_watch' instead - all th
On Mon, Feb 16, 2009 at 06:42:11PM -0500, Cole Robinson wrote:
> For some reason there are two VMDef members being used to keep track of
> monitor event handles: monitor_watch and monitorWatch. Remove the latter.
Can you remove the 'monitor_watch' instead - all the other variables
in the domain_co
For some reason there are two VMDef members being used to keep track of
monitor event handles: monitor_watch and monitorWatch. Remove the latter.
Thanks,
Cole
s/monitorWatch/monitor_watch/g
diff --git a/src/domain_conf.h b/src/domain_conf.h
index b6f6b43..b20cdec 100644
--- a/src/domain_conf.
