Date: Thu, 22 Jun 2006 10:42:40 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Johan =?utf-8?B?U3Ryw7Zt?= <johan@stromnet.org> Cc: freebsd-stable@freebsd.org Subject: Re: maxproc limit exceeded by uid 0 Message-ID: <20060622154240.GK9539@dan.emsphone.com> In-Reply-To: <6E52A605-0A6E-451B-AC25-33610E0D3838@stromnet.org> References: <F388196D-0353-4DF9-9A51-A88EBA01149A@stromnet.org> <449A4D78.5000106@gmx.de> <6E52A605-0A6E-451B-AC25-33610E0D3838@stromnet.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <pid>", then continue with "c". -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060622154240.GK9539>