From: Dave Benjamin <dave@ramenlabs.com>
To: David Allsopp <dra-news@metastack.com>
Cc: "'Caml List'" <caml-list@inria.fr>
Subject: Re: [Caml-list] Closing all open file descriptors
Date: Thu, 13 Sep 2007 23:41:51 -0700 [thread overview]
Message-ID: <46EA2D2F.4070108@ramenlabs.com> (raw)
In-Reply-To: <006b01c7f699$275fd6d0$017ca8c0@countertenor>
David Allsopp wrote:
> Probably irrelevant here, but this approach wouldn't work under Windows
> (Unix.file_descr is the Win32 file handle at that point which is often
> larger than 1024). More relevantly, Unix can be reconfigured to allow for
> more than 1024 open files.
Yes, I assumed that this would be non-portable, and that is yet another
problem. It seems that dropping down to C is the only way to really do
this right.
> Wouldn't an easier, portable way be to wrap Unix.openfile and Unix.close to
> maintain a set of open file_descrs or is your concern the risk of files left
> open by third party code?
The latter. The simple solution is to use Unix.set_close_on_exec from
the parent process, but that only works if it's under my control.
Dave
next prev parent reply other threads:[~2007-09-14 6:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 22:56 Dave Benjamin
2007-09-14 1:04 ` [Caml-list] " Erik de Castro Lopo
2007-09-14 6:35 ` Dave Benjamin
2007-09-14 6:48 ` Erik de Castro Lopo
2007-09-14 7:32 ` Dave Benjamin
2007-09-14 6:33 ` David Allsopp
2007-09-14 6:41 ` Dave Benjamin [this message]
2007-09-14 10:54 ` Andre Nathan
2007-09-14 10:00 ` Mattias Engdegård
2007-09-14 20:31 ` Dave Benjamin
2007-09-14 21:52 ` Oliver Bandel
2007-09-14 22:12 ` Markus E L
2007-09-15 9:15 ` Oliver Bandel
2007-09-15 9:26 ` Erik de Castro Lopo
2007-09-15 10:43 ` Oliver Bandel
2007-09-15 11:36 ` Mattias Engdegård
2007-09-15 11:57 ` Oliver Bandel
2007-09-15 14:27 ` Markus E L
2007-09-15 12:16 ` Oliver Bandel
2007-09-15 14:29 ` Markus E L
2007-09-15 18:04 ` skaller
2007-09-15 14:17 ` Markus E L
2007-09-15 14:16 ` Markus E L
2007-09-15 15:58 ` Eric Cooper
2007-09-15 16:17 ` Markus E L
2007-09-15 18:33 ` skaller
2007-09-15 17:44 ` skaller
2007-09-14 10:10 ` Gerd Stolpmann
2007-09-14 11:56 ` Oliver Bandel
2007-09-17 11:00 ` Ville-Pertti Keinonen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46EA2D2F.4070108@ramenlabs.com \
--to=dave@ramenlabs.com \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox