From owner-cvs-all@FreeBSD.ORG Mon Jul 19 17:28:42 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE31E16A4CE; Mon, 19 Jul 2004 17:28:42 +0000 (GMT) Received: from horsey.gshapiro.net (horsey.gshapiro.net [64.105.95.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id A39D943D2D; Mon, 19 Jul 2004 17:28:42 +0000 (GMT) (envelope-from gshapiro@gshapiro.net) Received: from horsey.gshapiro.net (localhost [127.0.0.1]) i6JHSg87050227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Jul 2004 10:28:42 -0700 (PDT) Received: (from gshapiro@localhost)i6JHSghk050226; Mon, 19 Jul 2004 10:28:42 -0700 (PDT) Date: Mon, 19 Jul 2004 10:28:42 -0700 From: Gregory Neil Shapiro To: Marcel Moolenaar Message-ID: <20040719172842.GC92908@horsey.gshapiro.net> References: <200407182028.i6IKS7Su002490@repoman.freebsd.org> <20040719034245.C32601@pooker.samsco.org> <20040719171041.GA22048@ns1.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040719171041.GA22048@ns1.xcllnt.net> User-Agent: Mutt/1.5.6i cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: Scott Long cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern imgact_elf.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2004 17:28:43 -0000 > > I've seen concern (maybe in private email, can't check at the moment) > > recently that loosing the PID info is undesirable. Is there any way that > > it can be included again, maybe in something other than a PRSTATUS object? Another option would be to record the PID in the file name (changing kern.corefile from %N.core to %N.%P.core for example). This has the added benefit of allowing for multiple cores if a buggy process dies more often than an admin can collect the cores. However, that benefit is also a disadvantage as it has disk-filling potential.