From: Vladimir Zhbanov <vzhbanov@gmail.com>
To: guile-user@gnu.org
Subject: Re: Pipes and processes, stdin, stdout and stderr
Date: Tue, 14 Apr 2015 19:41:40 +0300 [thread overview]
Message-ID: <20150414164140.GA5277@localhost.localdomain> (raw)
In-Reply-To: <873842yahs.fsf@earlgrey.lan>
[-- Attachment #1: Type: text/plain, Size: 144 bytes --]
Hi, Chris.
In geda-gaf, I modified open-pipe* to solve a similar issue.
See the procedure code and comments in attachment.
Cheers,
Vladimir
[-- Attachment #2: open-io-pipe.scm --]
[-- Type: text/plain, Size: 3544 bytes --]
;; run a child process and return a pair of input and output ports.
;; Executes the program 'command' with optional arguments 'args'
;; (all strings) in a subprocess.
;; Two ports to the process (based on pipes) are created and
;; returned.
;; The procedure is a modified version of the popen open-pipe*
;; procedure. Its functionality is close to that of
;; open-input-output-pipe. Changes are made to make it return two
;; ports instead of one in order to have a possibility to close
;; each one separately. This allows closing of the input pipe by
;; using (close-port port) when needed and emit EOF to the running
;; child process.
(define (gsch2pcb:open-io-pipe command . args)
(let* ((c2p (pipe)) ; child to parent
(p2c (pipe))) ; parent to child
(setvbuf (cdr c2p) _IONBF)
(setvbuf (cdr p2c) _IONBF)
(let ((pid (primitive-fork)))
(if (= pid 0)
(begin
;; child process
(ensure-batch-mode!)
;; select the three file descriptors to be used as
;; standard descriptors 0, 1, 2 for the new
;; process. They are pipes to/from the parent or taken
;; from the current Scheme input/output/error ports if
;; possible.
(let ((input-fdes (fileno (car p2c)))
(output-fdes (fileno (cdr c2p)))
(error-fdes
(or (false-if-exception (fileno (current-error-port)))
(open-fdes *null-device* O_WRONLY))))
;; close all file descriptors in ports inherited from
;; the parent except for the three selected above.
;; this is to avoid causing problems for other pipes in
;; the parent.
;; use low-level system calls, not close-port or the
;; scsh routines, to avoid side-effects such as
;; flushing port buffers or evicting ports.
(port-for-each (lambda (pt-entry)
(false-if-exception
(let ((pt-fileno (fileno pt-entry)))
(if (not (or (= pt-fileno input-fdes)
(= pt-fileno output-fdes)
(= pt-fileno error-fdes)))
(close-fdes pt-fileno))))))
;; Copy the three selected descriptors to the standard
;; descriptors 0, 1, 2, if not already there
(if (not (= input-fdes 0))
(begin
(if (= output-fdes 0) (set! output-fdes (dup->fdes 0)))
(if (= error-fdes 0) (set! error-fdes (dup->fdes 0)))
(dup2 input-fdes 0)
;; it's possible input-fdes is error-fdes
(if (not (= input-fdes error-fdes))
(close-fdes input-fdes))))
(if (not (= output-fdes 1))
(begin
(if (= error-fdes 1) (set! error-fdes (dup->fdes 1)))
(dup2 output-fdes 1)
;; it's possible output-fdes is error-fdes
(if (not (= output-fdes error-fdes))
(close-fdes output-fdes))))
(if (not (= error-fdes 2))
(begin
(dup2 error-fdes 2)
(close-fdes error-fdes)))
(apply execlp command command args)))
(begin
;; parent process
;; the forked child process should use these ports so
;; the parent process doesn't need them any more
(close-port (cdr c2p))
(close-port (car p2c))
;; return input and output ports
(cons (car c2p) (cdr p2c))
)))))
next prev parent reply other threads:[~2015-04-14 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 0:17 Pipes and processes, stdin, stdout and stderr Christopher Allan Webber
2015-04-14 16:41 ` Vladimir Zhbanov [this message]
2015-04-14 17:45 ` Christopher Allan Webber
2015-04-15 21:38 ` Thien-Thi Nguyen
2015-04-16 15:34 ` Christopher Allan Webber
2015-04-17 19:44 ` Thien-Thi Nguyen
2015-04-18 15:44 ` Mark H Weaver
2015-05-17 12:14 ` Pipes and processes, stdin, stdout and stderr -- ./configure in Guile Jan Nieuwenhuizen
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=20150414164140.GA5277@localhost.localdomain \
--to=vzhbanov@gmail.com \
--cc=guile-user@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).