X-Spam-Check-By: sourceware.org
Message-ID: <453037E1.8060208@byu.net>
Date: Fri, 13 Oct 2006 19:05:37 -0600
From: Eric Blake <ebb9@byu.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: How can I increase ulimit -n or open files limit to 65535 on  cygwin?
References: <31DDB7BE4BF41D4888D41709C476B65704169197@NIHCESMLBX5.nih.gov>
In-Reply-To: <31DDB7BE4BF41D4888D41709C476B65704169197@NIHCESMLBX5.nih.gov>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Buchbinder, Barry (NIH/NIAID) [E] on 10/13/2006 2:31 PM:
> Annie W. wrote:
>> can someone point me on how to increase open file limit?
>> Im stuck to 3200 on ulimit -n

You can't :(

At least, not without patching cygwin (and that is supposing that windows
even provides the hooks to make it possible).  Bash's ulimit on cygwin is
pretty much read-only.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFMDfh84KuGfSFAYARAlPUAJwOSa+YTzX7HpXdo8tCTsuOORIctACgn14H
VCgn7506NFlcW8anw4o1SVI=
=5IDR
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

