From owner-freebsd-questions@FreeBSD.ORG Tue Jul 27 18:18:47 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFE6716A4CE for ; Tue, 27 Jul 2004 18:18:47 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4DDC43D2F for ; Tue, 27 Jul 2004 18:18:47 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from working.potentialtech.com (pa-plum-cmts1e-68-68-113-64.pittpa.adelphia.net [68.68.113.64]) by internet.potentialtech.com (Postfix) with ESMTP id D0E8F69A39 for ; Tue, 27 Jul 2004 14:18:46 -0400 (EDT) Date: Tue, 27 Jul 2004 14:18:45 -0400 From: Bill Moran To: questions@freebsd.org Message-Id: <20040727141845.4e7cceb1.wmoran@potentialtech.com> Organization: Potential Technologies X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Postgres running in 5.1 jail corrupts Postgres running in host environment X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 18:18:48 -0000 I'm running Postgres 7.4 installed from a just cvsupped FreeBSD ports. I've got a production machine that's going to need a lot of upgrades, and I want to test them out prior to upgrading the production environment. So I built a jail on the production machine to install the new software in and test prior. Seems logical, right? Anyway, I set security.jail.sysvipc_allowed=1 so Postgres can run in the jail, but every time I start Postgres in the jail, the Postgres running in the host environ goes wacky. If I try to connect with psql, I get the following error: psql: FATAL: semctl(65542, 0, SETVAL, 0) failed: Invalid argument This is FreeBSD 5.1-p17 (I can't upgrade to 5.2.1 until the em driver is fixed ... but if someone knows for sure that this is fixed in 5.2.1, I'll push harder to get that driver fixed!) Anyone have any idea what's going wrong here? Or what I can do to fix it? -- Bill Moran Potential Technologies http://www.potentialtech.com