This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] [xend] fix coredump-{restart, destroy} on_crash

To: Jim Fehlig <jfehlig@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [xend] fix coredump-{restart, destroy} on_crash actions
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Tue, 27 Jul 2010 17:41:33 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 27 Jul 2010 09:42:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C4EF697.8060506@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Newsgroups: chiark.mail.xen.devel
References: <4C4EF697.8060506@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Jim Fehlig writes ("[Xen-devel] [PATCH] [xend] fix coredump-{restart, destroy} 
on_crash actions"):
> After all of these years, more fallout from xen-api and legacy xmlrpc
> integration.  Can't say I'll miss xend :-).
> Please apply to xen-4.0-testing.

We'll apply this to xen-unstable first, as Keir says.  However, I'm
not sure I fully understand how this patch works.

You're adding 'coredump_destroy' and 'coredump_restart' to the list of
allowable settings, but you don't appear to provide a corresponding
change to the implementation anywhere.  How does this work ?


Xen-devel mailing list