From owner-freebsd-stable@FreeBSD.ORG Thu Jun 22 15:43:01 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 3E8B716A47B for ; Thu, 22 Jun 2006 15:43:01 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D9B143D94 for ; Thu, 22 Jun 2006 15:42:59 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.4) id k5MFgeEU068210; Thu, 22 Jun 2006 10:42:40 -0500 (CDT) (envelope-from dan) Date: Thu, 22 Jun 2006 10:42:40 -0500 From: Dan Nelson To: Johan =?utf-8?B?U3Ryw7Zt?= Message-ID: <20060622154240.GK9539@dan.emsphone.com> References: <449A4D78.5000106@gmx.de> <6E52A605-0A6E-451B-AC25-33610E0D3838@stromnet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <6E52A605-0A6E-451B-AC25-33610E0D3838@stromnet.org> X-OS: FreeBSD 5.5-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: maxproc limit exceeded by uid 0 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: Thu, 22 Jun 2006 15:43:01 -0000 In the last episode (Jun 22), Johan Strm said: > On 22 jun 2006, at 09.57, [LoN]Kamikaze wrote: > >Johan Ström wrote: > >>Anyway.. I'm using default login.conf, which have unlimited for all > >>resource limits.. So wtf is this? > > > >Look at > > > ># sysctl kern.maxproc > > Okay, 4096 procs... But what was those 4k procs...On my newly booted > i got 127... Well I guess there is now way to find out now. If it ever happens again, you can drop to the debugger with Ctrl-Alt-ESC and run "ps" to get a list of running processes. You might even be able to recover by killing some offending processes with "kill 9 ", then continue with "c". -- Dan Nelson dnelson@allantgroup.com