On 08/09/11 - 10:26:53PM, Kashyap Chamarthy wrote:
On 08/09/2011 08:29 PM, Chris Lalancette wrote:
>On 08/09/11 - 08:51:43AM, Chris Lalancette wrote:
>>However, it seems like between the time that oz determined that the guest
>>didn't shut down, and when it actually went to do the kill, the domain shut
>>down of its own accord. This could just mean that the guest was slow in
>>This is a bug in Oz. If the destroy fails, but the guest has successfully gone
>>away, we should just ignore the error and succeed the operation. I'll take
>>look at fixing this today.
>I pushed a commit (ec18386d78940cb72552) to the Oz git repository that
>should take care of this problem.
>I've also attached the patch to this email. It should apply to version 0.5.0
>of Oz with some fuzz.
>If you get a chance, could you please give it a test and let me know if it
>works for you?
Ack. Thanks for the quick patch. git pull ; incremente the rel. no
in the oz.spec ; make rpm --> Works for me. Attached is the
successful package manifest generation.
Excellent, thanks for the test.
Minor nit: currently, the icicle(pkg manifest) xml config is spit
out to the stdout. Do you think a print to file option helps?
(Though this can be done with a bit of bash i/o redirection...)
Right. Actually, what I think might be a good thing is to keep the default
as it is (write ICICLE to stdout), but then add an option to write to a file
if the user wants. I'll add an option both to oz-install and
oz-generate-icicle to do that.