From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:59:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CF2E16A401 for ; Mon, 3 Apr 2006 03:59:19 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: from dbmail-mx1.orcon.net.nz (loadbalancer1.orcon.net.nz [219.88.242.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C72743D45 for ; Mon, 3 Apr 2006 03:59:17 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received-SPF: none Received: from heff.fud.org.nz (60-234-149-201.bitstream.orcon.net.nz [60.234.149.201]) by dbmail-mx1.orcon.net.nz (8.13.6/8.13.6/Debian-1) with SMTP id k333xupt022992; Mon, 3 Apr 2006 15:59:57 +1200 Received: by heff.fud.org.nz (Postfix, from userid 1001) id 675E21CC37; Mon, 3 Apr 2006 15:59:11 +1200 (NZST) Date: Mon, 3 Apr 2006 15:59:11 +1200 From: Andrew Thompson To: "Marc G. Fournier" Message-ID: <20060403035911.GA76193@heff.fud.org.nz> References: <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> <20060403002830.W947@ganymede.hub.org> <20060403034101.GA58429@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060403034101.GA58429@xor.obsecurity.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on dbmail-mx1.orcon.net.nz X-Virus-Status: Clean Cc: Tom Lane , pgsql-hackers@postgresql.org, freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 03:59:19 -0000 On Sun, Apr 02, 2006 at 11:41:01PM -0400, Kris Kennaway wrote: > On Mon, Apr 03, 2006 at 12:30:58AM -0300, Marc G. Fournier wrote: > > 'k, but how do I fix kill so that it has the proper behaviour if SysV is > > enabled? > > Check the source, perhaps there's already a way. If not, talk to > whoever made the change. > > > Maybe a mount option for procfs that allows for pre-5.x > > behaviour? > > procfs has nothing to do with this though. > > > I'm not the first one to point out that this is a problem, just > > the first to follow it through to the cause ;( And I believe there is > > more then just PostgreSQL that is affected by shared memory (ie. apache2 > > needs SysV IPC enabled, so anyone doing that in a jail has it enabled > > also) ... > > Also note that SysV IPC is not the problem here, it's the change in > the behaviour of kill() that is causing postgresql to become confused. > That's what you should investigate. The ESRCH error is being returned from prison_check(), that would be a good starting place. Andrew