9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] trying to understand how fork/pipe a filtering program
Date: Thu, 31 Aug 2006 21:15:46 +0100	[thread overview]
Message-ID: <f87e44514ae145d69d087ed932f5d38b@vitanuova.com> (raw)
In-Reply-To: <200608311955.k7VJtwv29679@demeter.cs.utwente.nl>

i'd have thought that something like the following should work:

	int p[2], q[2], kid, pid;
	Image *img;

	if(pipe(p) < 0 || pipe(q) < 0)
		sysfatal("can't make a pipe: %r");
	kid = fork();
	switch(kid){
	case -1:
		sysfatal("can't fork: %r");
	default:
		close(p[0]);
		close(q[1]);
		if (writeimage(p[1], from, 0) < 0)
			fprint(2, "error writeimage\n");
		close(p[1]);
		img = readimage(display, q[0], 0);
		close(q[0]);
		/*
		 * we may have unknown children forked by a previous
		 * program (e.g., rc) that then execed us.
		 */
		while ((pid = waitpid()) != kid && pid != -1)
			continue;
		return img;
	case 0:
		dup(p[0], 0);
		dup(q[1], 1);
		close(p[1]);
		close(q[0]);
		execl("/bin/resample", "resample", "-x50%", (char *)nil);
		sysfatal("can't exec resample: %r");
	}


  reply	other threads:[~2006-08-31 20:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30 22:46 Axel Belinfante
2006-08-30 23:05 ` geoff
2006-08-31 16:26 ` "Nils O. Selåsdal"
2006-08-31 19:55   ` Axel Belinfante
2006-08-31 20:15     ` rog [this message]
2006-08-31 20:24       ` Axel Belinfante
2006-08-31 20:24     ` rog
2006-08-31 20:45       ` Axel Belinfante
2006-09-01  3:43     ` geoff
2006-09-01 10:57       ` rog
2006-09-01 14:35 ` rog
2006-09-01 15:33   ` Skip Tavakkolian
2006-09-01 15:59     ` rog
2006-09-01 18:42       ` Skip Tavakkolian
2006-09-03 19:09   ` Axel Belinfante
2006-09-04 14:52     ` Gorka guardiola
2006-09-04 20:50       ` Gorka guardiola
2006-09-04 19:26     ` Skip Tavakkolian
2006-09-04 20:25       ` Francisco J Ballesteros

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=f87e44514ae145d69d087ed932f5d38b@vitanuova.com \
    --to=rog@vitanuova.com \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).