Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Xavier Leroy <xavier.leroy@inria.fr>
To: David Fox <david@lindows.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] process conundrum
Date: Fri, 15 Feb 2002 17:07:48 +0100	[thread overview]
Message-ID: <20020215170748.C14578@pauillac.inria.fr> (raw)
In-Reply-To: <87adudcb2l.fsf@foxthompson.net>; from david@lindows.com on Wed, Feb 13, 2002 at 01:43:14PM -0800

> Suppose I open a process to reverse the lines of a file like so:
> 
> # let readable, writable = 
>   Unix.open_process "cat -n | sort -n -r | sed 's:^[ 0-9]*[^ 0-9]::'";;
> 
> Then I write a few lines to it:
> Now I close the write end to cause an EOF, so the output arrives on readable:
> How do I cleanly terminate the process?
> # Unix.close_process (readable, writable);;
> Exception: Sys_error "Bad file descriptor".

This is indeed a bug in Unix.close_process: when it closes both
channels, it should not fail if the output channel is already closed.

Notice however a potential problem in your code: Unix pipes are
fixed-size buffers, so if you write a lot of data to one pipe, the
output pipe may fill up and the underlying process will block.  Thus,
Unix.open_process is usable only if you can alternate writes (of small
quantities) and reads, e.g. via two threads.  In other cases, it is
necessary to use an intermediate file, to hold either the input or the
output of the command.

- Xavier Leroy
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


      parent reply	other threads:[~2002-02-15 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13 21:43 David Fox
2002-02-14 13:42 ` Nicolas FRANCOIS
2002-02-15 16:07 ` Xavier Leroy [this message]

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=20020215170748.C14578@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=david@lindows.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