From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon, 19 May 2014 16:51:48 -0400
To: 9fans@9fans.net
Message-ID: <3b6bd7be273cb91515d8ededd002a3e4@ivey>
In-Reply-To: <CAEAzY3-4sG5i+ko-ctd9HSod=rhWaqDTOzuS9yG3x0BNuhnh7Q@mail.gmail.com>
References: <063412cb21a6433d959274d7db87d242@ladd.quanstro.net>
	<92606a17ce255a2e74049e4090d948b3@proxima.alt.za>
	<CAOw7k5h-y4-zBC5KOkeqLypLAp9rDouLj8r5Eok8EvxOhLhdCw@mail.gmail.com>
	<a3b937311c3c09f698cc70b455642d6d@ladd.quanstro.net>
	<CAEAzY3-4sG5i+ko-ctd9HSod=rhWaqDTOzuS9yG3x0BNuhnh7Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] syscall 53
Topicbox-Message-UUID: e8cc1716-ead8-11e9-9d60-3106f5b1d025

> There was another complaint about /dev/bintime. Some people claimed
> that using it leaked file descriptors in multithreaded programs. I
> don't understand why this problem can't be solved by opening it
> close-on-exec. In fact, this problem doesn't exist in the port of
> Go to Plan 9 anymore (although the fix was different)...

close-on-exec doesn't solve any interesting issues.  close on fork might,
but we don't have that.

if two threads share memory, but do not share file descriptor tables, or
if you overflow the file descriptor array, you're really cooked.  things go
seriously wrong in a hurry.

there are other cases that are really terrible, but this is the most glaring one.

- erik