From owner-freebsd-hackers Mon Jan 22 21:33:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA01651 for hackers-outgoing; Mon, 22 Jan 1996 21:33:55 -0800 (PST) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA01645 for ; Mon, 22 Jan 1996 21:33:52 -0800 (PST) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.6.11/8.6.9) with ESMTP id VAA13257; Mon, 22 Jan 1996 21:33:34 -0800 From: Josh MacDonald Message-Id: <199601230533.VAA13257@paris.CS.Berkeley.EDU> To: davidg@root.com cc: Josh MacDonald , Warner Losh , Wolfram Schneider , hackers@freebsd.org, jmacd@paris.CS.Berkeley.EDU Subject: Re: recursive grep In-reply-to: Your message of "Mon, 22 Jan 1996 21:27:44 PST." <199601230527.VAA17805@Root.COM> Date: Mon, 22 Jan 1996 21:33:32 -0800 Sender: owner-hackers@freebsd.org Precedence: bulk > >Oh, well anyhow _SC_ARG_MAX is set at 64k which I have found exceedingly > >low. How do you change this anyways? > > It's not easily changed without causing other problems. 64K already result >s > in potentially 1MB of memory being temporarily consumed. I need to make some > changes to kern_exec.c to add support for a resource wait when "string" space > isn't allocateable. Right now it returns ENOMEM if more than 16 processes > simultaneously exec. This is an extremely rare condition, but possible. I shouldn't really be contributing much to this conversation because I don't know the first thing about this at the kernel level, but from the programmer level, I've noticed this limit. On this weak old Sun the limit is 1M for _SC_ARG_MAX. I guess its better that I noticed the limit because it forced me to write code for a situation I was hoping would never arise. -josh