Date: Sat, 4 Oct 1997 14:19:19 -0400 (EDT) From: Paul Sandys <myj@nyct.net> To: Bob Willcox <bob@luke.pmr.com> Cc: stable list <freebsd-stable@FreeBSD.ORG> Subject: Re: fork errors - resource temporarily unavailable Message-ID: <Pine.BSF.3.96.971004140954.4926A-100000@bsd3.nyct.net> In-Reply-To: <19971003100413.33095@pmr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 3 Oct 1997, Bob Willcox wrote: > Date: Fri, 3 Oct 1997 10:04:13 -0500 > From: Bob Willcox <bob@pmr.com> > Reply-To: Bob Willcox <bob@luke.pmr.com> > To: stable list <freebsd-stable@FreeBSD.ORG> > Subject: fork errors - resource temporarily unavailable > > Every since I upgraded my system to 2.2-STABLE a couple of months ago I > have been having this temporary but re-occuring problem with procmail > getting EAGAIN errors when trying to fork one or more of the programs > that I have specified in my .procmailrc file. I believe my limits are > sufficiently high: > > Resource limits (current): > cputime infinity secs > filesize infinity kb > datasize-cur 32768 kb > stacksize 8192 kb > coredumpsize 8192 kb > memoryuse-cur 32768 kb > memorylocked 10240 kb > maxprocesses 512 > openfiles-cur 512 I had same problem here. I tracked it down to sendmail being started from /etc/rc scripts with limits of 32 processes or so. My theory is, that at the moment procmail changes UID to yours, it still checks against limits from startup. I cured this by unlimiting all resources in my /etc/rc. Starting sendmail from unlimited shell also fixes the problem. This also brings the question about default limits processing. These are limits on my RELENG_2_2 machine during boot: Resource limits (current): cputime infinity secs filesize 65536 kb datasize-cur 16384 kb stacksize-cur 8192 kb coredumpsize 0 kb memoryuse-cur 65536 kb memorylocked-cur 65536 kb maxprocesses 32 openfiles-cur 64 At the same time, I've got following lines in my kernel config file: options "CHILD_MAX=1024" options "OPEN_MAX=1024" options "FD_SETSIZE=1024" I believed, that above will raise my default limits, but it doesn't seem to be happening. > > as I never have more than about 150 or so processes running on my > system, yet procmail (and only procmail!) intermittantly has this > problem. > > Note that I have upgraded my system a few times since I first started > seeing this problem (right now I'm running 2.2-stable as of about 5 days > ago), yet the problem persists. > > Any help or advice will be greatly appreciated. > > Thanks, > -- > Bob Willcox Deliberation, n.: The act of examining one's bread > bob@luke.pmr.com to determine which side it is buttered on. > Austin, TX -- Ambrose Bierce, "The Devil's Dictionary" > P. <-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-> < myj@nyct.net Paul Sandys | New York Connect http://www.nyct.net > < network operations manager | Total Solution provider > <-------------------------------------------------------------------------> < " BRINGING NEW YORK THE INTERNET SERVICES IT DESERVES " > <-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_->
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971004140954.4926A-100000>