From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST] Arrange for core dumps to be placed in /var/core and collect them
Date: Wed, 25 Mar 2015 09:40:50 +0000 [thread overview]
Message-ID: <1427276450.10784.25.camel@citrix.com> (raw)
In-Reply-To: <21777.44652.634423.829345@mariner.uk.xensource.com>
On Tue, 2015-03-24 at 18:35 +0000, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH OSSTEST] Arrange for core dumps to be placed in /var/core and collect them"):
> > On Tue, 2015-03-24 at 12:40 +0000, Ian Jackson wrote:
> > > I think you should add /var/core to the leak check step.
> >
> > Which in practice just means listing it in the arugment to
> > inventory_files?
>
> Yes.
Good, v2 in <1427207038-28090-1-git-send-email-ian.campbell@citrix.com>
does just that.
Do you have any thoughts on how to best universally arrange for the
rlimits to be increased? Probably inserting a ulimit call into the
libvirt initscript would be an easy first step, and since that's the
thing we most often see crashing it seems. I'll send such a patch
shortly.
Adding it to xencommons would be OK too, which just leaves catching e.g.
daemonised xl processes launched via ssh. Hacking /etc/profile or
something in TestSupport::cmdex perhaps?
Ian.
next prev parent reply other threads:[~2015-03-25 9:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 15:40 [PATCH OSSTEST] Arrange for core dumps to be placed in /var/core and collect them Ian Campbell
2015-03-09 21:54 ` Don Slutz
2015-03-10 9:38 ` Ian Campbell
2015-03-24 12:40 ` Ian Jackson
2015-03-24 12:46 ` Ian Campbell
2015-03-24 18:35 ` Ian Jackson
2015-03-25 9:40 ` Ian Campbell [this message]
2015-03-25 14:38 ` Ian Campbell
2015-03-25 16:18 ` Ian Jackson
2015-03-25 16:30 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1427276450.10784.25.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.