From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH OSSTEST] Arrange for core dumps to be placed in /var/core and collect them Date: Wed, 25 Mar 2015 14:38:24 +0000 Message-ID: <1427294304.10784.86.camel@citrix.com> References: <1425915623-14878-1-git-send-email-ian.campbell@citrix.com> <21777.23376.332679.268338@mariner.uk.xensource.com> <1427201206.21742.389.camel@citrix.com> <21777.44652.634423.829345@mariner.uk.xensource.com> <1427276450.10784.25.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1427276450.10784.25.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Wed, 2015-03-25 at 09:40 +0000, Ian Campbell wrote: > 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? I handled this by writing an /etc/security/limits.d/ file during host install, which seems to have done the trick. I just sent a patch which along with the libvirt one I sent earlier today covers everything I think we care about except our daemons which are launched from xencommons. The initscript in xen.git doesn't offer a useful hook for this, we could add something to the end of /etc/default/xencommons, which is sourced by the script, but that seems like a bit of an abuse. Ian.