summaryrefslogtreecommitdiff
path: root/tools/pipette.c
diff options
context:
space:
mode:
Diffstat (limited to 'tools/pipette.c')
-rw-r--r--tools/pipette.c28
1 files changed, 15 insertions, 13 deletions
diff --git a/tools/pipette.c b/tools/pipette.c
index c76b9e5..69e75be 100644
--- a/tools/pipette.c
+++ b/tools/pipette.c
@@ -94,26 +94,26 @@ typedef enum {MSG, ENV} channeler;
/*
Notation for future use:
- 0< &kb 1> &scr 2> &scr prog1 # stand-alone
- 0< &kb 1> &redpipe 2> &scr prog2 # upstream end of pipe
- 0< &redpipe 1> &scr 2> &scr prog3 # downstream end of pipe
+ 0< kb 1> scr 2> scr prog1 # stand-alone
+ 0< kb 1> pipe 2> scr prog2 # upstream end of pipe
+ 0< pipe 1> scr 2> scr prog3 # downstream end of pipe
- 0< &msg 1< &envelope 2> &log qmail-queue
+ 0< msg 1< envel 2> log qmail-queue
- 0< &kb 1> &scr 2> &scr 7> &up 8< &down parent
- 0< &up 1> &down 2> &scr childprocess
+ 0< kb 1> scr 2> scr 7> up 8< down parent
+ 0< up 1> down 2> scr childprocess
Simple case:
- 0< &msg 1> &msg2 2> &log skrewt
- 0< &msg2 1> &msg3 2> &log spamc
- 0< &msg3 1< &envelope 2> &log qmail-queue
+ 0< msg 1> msg2 2> log skrewt
+ 0< msg2 1> msg3 2> log spamc
+ 0< msg3 1< envel 2> log qmail-queue
Fancier "triangular piping" case:
- 0< &msg 1< &env 2> &log 7> &msg2 8> &env2 skrewt
- 0< &msg2 1> &msg3 2> &log spamc
- 0< &msg3 1< &env2 2> &log qmail-queue
+ 0< msg 1< env 2> log 6> msg2 7< sts 8> env2 skrewt
+ 0< msg2 1> msg3 2> log 8> sts spamc
+ 0< msg3 1< env2 2> log qmail-queue
-Note that units 7 and 8 are arbitrary and could be renumbered. In
+Note that units 6, 7, and 8 are arbitrary and could be renumbered. In
contrast, many of the other are fixed by standards and/or traditions.
Some questions:
@@ -126,6 +126,8 @@ Similarly, now hard is it to detect a /broken/ pipe segment, i.e. one
where all the reading ends have been closed? This means the writing
ends can be closed, freeing up FD units.
+See also notes in ./makefile
+
*/
typedef enum {series, stub, sa, qq, postspam, fail} moder;