From: Oliver Bandel <oliver@first.in-berlin.de>
To: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Closing all open file descriptors
Date: Fri, 14 Sep 2007 23:52:08 +0200 [thread overview]
Message-ID: <1189806728.46eb0288d38b8@webmail.in-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0709141528570.27531@tenhost.net>
Zitat von Dave Benjamin <dave@ramenlabs.com>:
> On Fri, 14 Sep 2007, Mattias Engdegård 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.
> >
> > I think platform-dependent code is required here. The common way of
> > doing this under Linux (and Solaris, probably) is to readdir
> > /proc/PID/fd/. Windows is of course very different.
>
> I like this approach. It doesn't eliminate the need to convert ints to
> descrs,
On Unix, file-descriptors are identified by integer-values.
In OCaml, you have abstract types for file-descriptors.
So, how to convert them? I think, officially there is no way.
But if you like the concept of completely using files,
Plan9 as operating system would make sense to you. :)
> but at least you don't have a bunch of unnecessary system calls or
> a hard-coded maximum
Something like Sys.max_open_fd would be fine,
and I think there should be a way to make it cross-platform-available.
> (assuming getrlimit is unavailable, as it is with
> OCaml currently).
getrlimit seems to be a Unix-only thing.
I don't know if this is also available on other systems, like Windows or so.
So, if it is Unix-specific, this only would make sense in the Unix-modlue.
But something like the maximum number of open files / max-num of
used filedescriptors would also make sense on unix.
So, I would ask for something like a Sys.max_open_fd.
This owuld be a cross-platform thing.
> I wonder if /dev/fd is more or less portable...
Will this be available on non-Unix and non-Linux systems?
You also mentioned Win-systems?
If you also need that portability, you should not look for
Unix-only features.
Ciao,
Oliver
next prev parent reply other threads:[~2007-09-14 21:51 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
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 [this message]
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=1189806728.46eb0288d38b8@webmail.in-berlin.de \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
/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