From owner-freebsd-questions@FreeBSD.ORG Sun Jun 26 21:32:37 2005 Return-Path: X-Original-To: freebsd-questions@FreeBSD.org 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 7E90116A41C for ; Sun, 26 Jun 2005 21:32:37 +0000 (GMT) (envelope-from mbsd@pacbell.net) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4114143D53 for ; Sun, 26 Jun 2005 21:32:37 +0000 (GMT) (envelope-from mbsd@pacbell.net) Received: from pimout7-ext.prodigy.net (pimout7-int.prodigy.net [207.115.4.147]) by ylpvm15.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id j5QLWn57006922 for ; Sun, 26 Jun 2005 17:32:49 -0400 X-ORBL: [64.166.22.206] Received: from sotec.home (adsl-64-166-22-206.dsl.snfc21.pacbell.net [64.166.22.206]) by pimout7-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id j5QLWRZL051946 for ; Sun, 26 Jun 2005 17:32:32 -0400 Date: Sun, 26 Jun 2005 14:32:25 -0700 (PDT) From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= X-X-Sender: mikko@sotec.home To: freebsd-questions@FreeBSD.org In-Reply-To: <20050626205620.GC89575@keyslapper.net> Message-ID: <20050626142104.L1638@sotec.home> References: <20050626191706.GB89575@keyslapper.net> <20050626223917.3b50913b.albi@scii.nl> <20050626205620.GC89575@keyslapper.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Re: Perl 5.8.6 to 5.8.7 upgrade fails IPC tests X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jun 2005 21:32:37 -0000 On Sun, 26 Jun 2005, Louis LeBlanc wrote: > On 06/26/05 10:39 PM, albi@scii.nl sat at the `puter and typed: >> On Sun, 26 Jun 2005 15:17:06 -0400 >> Louis LeBlanc wrote: >> >>> I'm having a little trouble with my perl upgrade from 5.8.6 to 5.8.7. >> -- cut -- >>> ok 5 >>> ok 6 >>> semget: No space left on device >> >> you need to make disc-space, one idea is to run portsclean -C or to make >> some more space in /usr/home > > That would be the obvious cause, but not so: [...] Indeed. Disk space most likely has nothing to do with it. The semget(2) call returns ENOSPC when unable to allocate semaphores, due to hitting one of the many SYSV IPC limitations. Some things to look for: - You need to have SYSVSEM in your kernel, or "sysvsem.ko" loaded. - Check semaphore limits with "ipcs -S" - Check current semaphore usage with "ipcs -s" - Figure out what limit is being hit and do something about it :-) Some of the values can be tweaked at run-time, with "sysctl kern.ipc.semxxx=value", others have to be set at boot time (in /boot/loader.conf), or compiled into the kernel. $.02, /Mikko