@@ -11,12 +11,13 @@ pipexec [OPTION]... [PROCESS DESCRIPTION]... [PIPE DESCRIPTION]...
1111.SH DESCRIPTION
1212.B pipexec
1313creates an arbitrary network (directed graph) of processes and pipes
14- in between. Even cycles are possible. It overcomes the shortcomings
14+ in between - even cycles are possible. It overcomes the shortcomings
1515of shells that are typically only able to create non cyclic trees.
1616.P
1717.B pipexec
18- also monitors all it's processes and is able to restart the whole
19- network of processes and pipes if one process crashes. Therefore
18+ also monitors all it's child processes and is able to restart the
19+ whole network of processes and pipes if one crashes.
20+ Therefore
2021.B pipexec
2122can be used in SYSV-init or systemd configuration to run a network of
2223processes.
@@ -26,15 +27,15 @@ processes.
2627print help and version information
2728.TP
2829\fB \- l logfd \fR
29- use the given log file descriptor for logging. If a 's' is specified,
30+ use the given file descriptor for logging. If a 's' is specified,
3031syslog is used. Example: Specifying '2' means log to stderr.
3132.TP
3233\fB \- p pidfile \fR
3334with
3435.B pipexec
3536it is possible to handle pipes within SYSV-init scripts. In some
3637environments (e.g. RHEL6, Debian7) the start and stop routines need a
37- pid file. If this option is given, pipexec writes it own pid into the
38+ pid file. If this option is given, pipexec writes its own pid into the
3839file shortly after start of pipexec.
3940.TP
4041\fB \- k \fR
@@ -78,7 +79,7 @@ e.g. pass a fd of 'wc' either to 'grep' or to 'find'.
7879overcomes these limitations. It makes it possible to link any two
7980arbitrary file descriptors in a set of processes.
8081.SH USAGE
81- Building up a network of processes and pipes, there is the need to
82+ When building up a network of processes and pipes, there is the need to
8283specify each element separately.
8384.P
8485The processes will be the nodes in the network (directed graph), the
0 commit comments