unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Chris Vine <chris@cvine.freeserve.co.uk>
To: Guile-devel <guile-devel@gnu.org>
Subject: Re: fork pipe dup2 exec
Date: Wed, 17 Aug 2016 15:09:28 +0100	[thread overview]
Message-ID: <20160817150928.468f78f2@bother.homenet> (raw)
In-Reply-To: <CAJ=RwfZr9rvNNTVyC9Gp=5iCwJE92L-uZ4VcfOxsU7gtKUiUzw@mail.gmail.com>

On Wed, 17 Aug 2016 09:56:58 -0400
"Thompson, David" <dthompson2@worcester.edu> wrote:
> On Wed, Aug 17, 2016 at 9:35 AM, Tobias Reithmaier
> <tobi3489@yahoo.de> wrote:
> > Hello,
> >
> > is there a way to program a Inter Process Communication (IPC) in
> > guile like you do it with the Linux-Libc-API with the combo fork,
> > pipe, dup2 and exec? If you use the popen-module it's not the same
> > because you have to wait until the program has finished.
> > But there are use-cases in that the program doesn't finish. e.g. a
> > server which outputs data every minute.
> >
> > So can i use the popen-module to control such a server with pipes?
> > Or is there another way?  
> 
> Check out the "POSIX" section of the manual. Fork, dup, and exec are
> all available.

Tobias might also want to consider the run-with-pipe procedure, and the
run-concurrently+ procedure (with tail-call-program), as provided by
guile-lib ( http://www.nongnu.org/guile-lib/doc/ref/os.process/ ).

Tobias looks as if he has posted to the wrong newsgroup.  Follow ups
should I think go to guile-user (but I have not set them).

Chris



  reply	other threads:[~2016-08-17 14:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <630665159.26184630.1471440950603.JavaMail.yahoo.ref@mail.yahoo.com>
2016-08-17 13:35 ` fork pipe dup2 exec Tobias Reithmaier
2016-08-17 13:56   ` Thompson, David
2016-08-17 14:09     ` Chris Vine [this message]
2016-08-18  9:22       ` Tobias Reithmaier

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160817150928.468f78f2@bother.homenet \
    --to=chris@cvine.freeserve.co.uk \
    --cc=guile-devel@gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).