From owner-freebsd-questions@FreeBSD.ORG Tue Dec 7 20:10:20 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DF6A10656DD for ; Tue, 7 Dec 2010 20:10:20 +0000 (UTC) (envelope-from cyberleo@cyberleo.net) Received: from paka.cyberleo.net (paka.cyberleo.net [66.219.31.21]) by mx1.freebsd.org (Postfix) with ESMTP id EBA768FC20 for ; Tue, 7 Dec 2010 20:10:19 +0000 (UTC) Received: from [172.16.44.4] (den.cyberleo.net [66.253.36.39]) by paka.cyberleo.net (Postfix) with ESMTPSA id E846529619; Tue, 7 Dec 2010 15:10:18 -0500 (EST) Message-ID: <4CFE94AA.7060002@cyberleo.net> Date: Tue, 07 Dec 2010 14:10:18 -0600 From: CyberLeo Kitsana User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.9) Gecko/20100911 Lightning/1.0b3pre Thunderbird/3.1.3 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4CF9C1E5.3070101@rawbw.com> <44r5dw88yd.fsf@lowell-desk.lan> In-Reply-To: <44r5dw88yd.fsf@lowell-desk.lan> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Yuri , Lowell Gilbert Subject: Re: portupgrade causes kernel message: maxproc limit exceeded by uid 0 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: Tue, 07 Dec 2010 20:10:20 -0000 On 12/05/2010 10:45 AM, Lowell Gilbert wrote: > Yuri writes: > >> Beginning at some time less than 1 month ago I started getting such >> message. Increasing maxproc doesn't help. Current values are like >> this: >> kern.maxproc: 6164 >> kern.maxprocperuid: 5547 >> >> What may be causing such condition? > > limits(1), perhaps? I DoSed a remote box building devel/glib20 too. Just now reproduced it locally. It manifested as a forkbomb somewhere in gnome-libtool while building glib-2.26.1 inside a clean chroot (not a jail). The issue seemed to only manifest within the chroot, regardless of whether the configuration was identical to the host or not. It did not occur when attempting to build on the host machine. Every other package I built worked just fine. I eventually tracked it down to a stray colon at the start of the PATH variable in my chroot build environment: PATH=:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Thus, it might be a good idea to verify that your build environment variables and config files are sane. ========== mv -f .deps/gdatetime.Tpo .deps/gdatetime.Po /bin/sh /usr/obj/usr/ports/devel/glib20/work/gnome-libtool --tag=CC --mode=link cc -O2 -pipe -O2 -pipe -march=nocona -fno-strict-aliasing -Wall -L/usr/local/lib -lintl -o strfuncs strfuncs.o ../../glib/libglib-2.0.la -lm mv -f .deps/regex.Tpo .deps/regex.Po /bin/sh /usr/obj/usr/ports/devel/glib20/work/gnome-libtool --tag=CC --mode=link cc -O2 -pipe -O2 -pipe -march=nocona -fno-strict-aliasing -Wall -L/usr/local/lib -lintl -o string string.o ../../glib/libglib-2.0.la -lm printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable /libexec/ld-elf.so.1: Shared object "libglib-2.0.so.0" not found, required by "printf" ========== -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Furry Peace! - http://wwww.fur.com/peace/