Extended new command -named_pipe_loop by mode parameter
This commit is contained in:
@ -9,7 +9,7 @@
|
||||
.\" First parameter, NAME, should be all caps
|
||||
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
|
||||
.\" other parameters are allowed: see man(7), man(1)
|
||||
.TH XORRISO 1 "Version 1.3.1, Jul 02, 2013"
|
||||
.TH XORRISO 1 "Version 1.3.1, Jul 03, 2013"
|
||||
.\" Please adjust this date whenever revising the manpage.
|
||||
.\"
|
||||
.\" Some roff macros, for reference:
|
||||
@ -4700,19 +4700,30 @@ Above example "SORRY,UPDATE" will yield 1.
|
||||
Print to the result channel a blank separated list of all severity names.
|
||||
Sorted from low to high severity.
|
||||
.TP
|
||||
\fB\-named_pipe_loop\fR disk_path_stdin disk_path_stdout disk_path_stderr
|
||||
\fB\-named_pipe_loop\fR mode[:mode] disk_path_stdin disk_path_stdout disk_path_stderr
|
||||
Temporarily replace standard input, standard output and standard error by
|
||||
named pipes. Enter dialog mode without readline.
|
||||
The three parameters must either be disk paths to existing named pipes,
|
||||
.br
|
||||
Defined modes are:
|
||||
.br
|
||||
"cleanup" removes the submitted pipe files when the loop ends.
|
||||
.br
|
||||
"keep" does not delete them. This is the default.
|
||||
.br
|
||||
"buffered" reads all lines from the input pipe until EOF before it opens
|
||||
the output pipes and processes the input lines.
|
||||
.br
|
||||
"direct" opens the output pipes after the first input line was read.
|
||||
Each line is executed directly after it is read. This is the default.
|
||||
.br
|
||||
The other three parameters must either be disk paths to existing named pipes,
|
||||
or be "\-" to leave the according standard i/o channel unreplaced.
|
||||
.br
|
||||
xorriso will open the stdin pipe, read and execute dialog lines from it
|
||||
until the sender closes the pipe. Then xorriso will close its side of
|
||||
the pipes and enter a new cycle of opening, reading and executing.
|
||||
.br
|
||||
The output pipes will get opened after the first input line was
|
||||
read from a freshly opened pipe. This allows the sender to first send
|
||||
a very long line and to only then open an output pipe for reading the reply.
|
||||
until the sender closes the pipe. The output pipes get opened depending on
|
||||
mode "buffered" resp. "direct". After all lines are executed, xorriso will
|
||||
close its side of the pipes and enter a new cycle of opening, reading and
|
||||
executing.
|
||||
.br
|
||||
If an input line consists only of the word "end_named_pipe_loop"
|
||||
then \-named_pipe_loop will end and further xorriso commands may be
|
||||
|
Reference in New Issue
Block a user