From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-35874-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 7551 invoked by alias); 23 Jul 2015 17:47:53 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 35874
Received: (qmail 11538 invoked from network); 23 Jul 2015 17:47:51 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,
	RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no
	version=3.4.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=usoAARNOlP1FRJu38/O/kUHsGzeJ+/ffQIgLNwJEH3U=;
        b=CwImXKQDWmoiE7Gflj5ly0Q9zGYlM/Zai0JG/h/zr7kvl5S9KRlKBY+SDp0pmGRjDn
         uZDTrlS8Rs42liUjRzsgo+VnHmP6Oh3gXRYYRjuesvEa6EwnLq+u8xYAniU7QeBPjoj/
         7bV7SU2qNf6ZFwIbMmHc/MPV0U5zuxL1tGXJwjhK64jzttRSJkXxWX/qlCU5t5NH4hxm
         zDBtMkU5EljGbpXqf0GeO3TWekHr45gLRXblVMr0uRwi8mlgOHFjMCh/nu/uZmWv6BZP
         A1/txGRG92NpNqxwPnNwQbX1Cjy3uksxs9UsToeEtmE5hHB4Xanjt4+cBFKrX71IcaW4
         4t1A==
X-Received: by 10.182.40.165 with SMTP id y5mr10207750obk.21.1437673665641;
 Thu, 23 Jul 2015 10:47:45 -0700 (PDT)
MIME-Version: 1.0
From: JD Ballard <i.am.qix@gmail.com>
Date: Thu, 23 Jul 2015 17:47:36 +0000
Message-ID: <CADYt08Yf2QWcZ--Uh4qKVGE8xE4L0tDYne76dBjOtPYWwKh1oQ@mail.gmail.com>
Subject: Maximum of 9 file descriptors
To: zsh-workers@zsh.org
Content-Type: multipart/alternative; boundary=001a11c32e0624c4a9051b8e7c81

--001a11c32e0624c4a9051b8e7c81
Content-Type: text/plain; charset=UTF-8

Is there a reason why file descriptors are maxed out at 9?

    $ zsh
    $ cat 9>/tmp/foo # works
    $ cat 10>/tmp/foo # error

With Bash, this isn't the case.

    $ bash
    $ cat 9>/tmp/foo # works
    $ cat 10>/tmp/foo # also works

--001a11c32e0624c4a9051b8e7c81--