From owner-freebsd-isp Sat Jan 6 17:35:36 2001 From owner-freebsd-isp@FreeBSD.ORG Sat Jan 6 17:35:19 2001 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from hawk-systems.com (unknown [161.58.152.235]) by hub.freebsd.org (Postfix) with ESMTP id 95BC437B402 for ; Sat, 6 Jan 2001 17:35:18 -0800 (PST) Received: from server0 (cr901664-a.pr1.on.wave.home.com [24.112.146.66]) by hawk-systems.com (8.8.8) id SAA17777 for ; Sat, 6 Jan 2001 18:33:43 -0700 (MST) From: "Dave VanAuken" To: Subject: determine if sysv running/avaialble within a jail Date: Sat, 6 Jan 2001 20:41:43 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org posting here because no one else in the other lists has two bits of knowledge about jails. is there a surefire way to test if sysv is operational within the jail... even if it will not release various memory blocks for use? FreeBSD 4.2 Release sysv memory apparently working and function under host machine cannot to ipcclean and other sysv function, but am not sure if this is a result of those commands not being allowed within the jail or because the sysv memory still isn't available from within the jail. jail'ed environment, ** jail.sysv_allowed is set to 1 on host ** appreciate the input yet again, this is a last attempt as getting this jail off the ground before going to a chroot based virtual server type of solution. Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message