Changed the parameter rules for new command -launch_frontend
This commit is contained in:
@ -4014,10 +4014,9 @@ File: xorriso.info, Node: Frontend, Next: ExDevices, Prev: Scripting, Up: Co
|
||||
*list_sev*
|
||||
Print to the result channel a blank separated list of all severity
|
||||
names. Sorted from low to high severity.
|
||||
-launch_frontend program_with_args command_pipe reply_pipe
|
||||
Start the program that is given as first word in parameter
|
||||
program_with_args. Submit the other words from that parameter as
|
||||
program arguments. Enable xorriso dialog mode.
|
||||
-launch_frontend program [arguments ...] --
|
||||
Start the program that is given as first parameter. Submit the
|
||||
other parameters as program arguments. Enable xorriso dialog mode.
|
||||
xorriso will abort when the started program ends or if it cannot
|
||||
be started at all. In both cases it will return a non-zero exit
|
||||
value. The exit value will be zero if the frontend sends -end or
|
||||
@ -4026,40 +4025,23 @@ File: xorriso.info, Node: Frontend, Next: ExDevices, Prev: Scripting, Up: Co
|
||||
default if xorriso runs under setuid permissions.
|
||||
The program name will not be searched in the $PATH directories.
|
||||
To make this clear, it must contain at least one /-character.
|
||||
Best is an absolute path. Like: /usr/bin/wish
|
||||
If one of command_pipe and reply_pipe is empty, then two nameless
|
||||
pipe objects are created. xorriso standard input gets connected to
|
||||
the standard output of the started program. xorriso standard
|
||||
output and standard error get connected to the standard input of
|
||||
that program.
|
||||
Best is an absolute path.
|
||||
The frontend program should first send via its standard output:
|
||||
-mark 0 -pkt_output on -msg_op start_sieve -
|
||||
-mark 0 -pkt_output on -msg_op start_sieve - -reassure off
|
||||
It should be ready to decode -pkt_output and to react on -mark
|
||||
messages. Best is to increment the -mark number after each sent
|
||||
command sequence and then to wait for the new number to show up in
|
||||
a mark message:
|
||||
some ... commands -mark <incremented_number>
|
||||
...some...commands... -mark <incremented_number>
|
||||
Further are advised:
|
||||
-report_about UPDATE -abort_on NEVER
|
||||
-iso_rr_pattern off -disk_pattern off
|
||||
A check of the xorriso version should be done, in order to make
|
||||
sure that all desired features are present.
|
||||
If command_pipe and reply_pipe are not empty, then create named
|
||||
pipes with these names and use them for the connection to the
|
||||
standard input and standard output of the started program. It is
|
||||
not an error if the named pipes already exist.
|
||||
With named pipes it is important that the frontend program opens
|
||||
the command_pipe first. This is because xorriso will block at this
|
||||
pipe until the frontend opens it. If the frontend would try to
|
||||
open reply_pipe first, then it would block there and create a
|
||||
deadlock situation.
|
||||
Command -launch_frontend will only work once per xorriso run. If
|
||||
all three command parameters are submitted as empty texts, then no
|
||||
program will be started but nevertheless -launch_frontend will be
|
||||
irrevocably disabled. If parameter program_with_args is submitted
|
||||
as empty text and both pipe parameters are non-empty, then no
|
||||
program will be started but the standard i/o channels of xorriso
|
||||
will get connected to named pipes.
|
||||
no command parameters are submitted or if program is an empty text,
|
||||
then no program will be started but nevertheless -launch_frontend
|
||||
will be irrevocably disabled.
|
||||
|
||||
-prog text
|
||||
Use text as name of this program in subsequent messages
|
||||
@ -4825,8 +4807,8 @@ File: xorriso.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: Top
|
||||
* -print_info prints message text line: Scripting. (line 102)
|
||||
* -print_mark prints synchronizing text line: Scripting. (line 105)
|
||||
* -print_size predicts image size: Inquiry. (line 91)
|
||||
* -prog sets program name: Frontend. (line 160)
|
||||
* -prog_help prints help text: Frontend. (line 163)
|
||||
* -prog sets program name: Frontend. (line 142)
|
||||
* -prog_help prints help text: Frontend. (line 145)
|
||||
* -prompt prompts for enter key: Scripting. (line 110)
|
||||
* -publisher sets publisher id: SetWrite. (line 186)
|
||||
* -pvd_info shows image id strings: Inquiry. (line 104)
|
||||
@ -4983,6 +4965,8 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
|
||||
* Filter, show chains of tree, -show_stream_r: Navigate. (line 183)
|
||||
* Filter, unregister, -unregister_filter: Filter. (line 48)
|
||||
* Filter, zisofs parameters, -zisofs: SetWrite. (line 272)
|
||||
* Frontend program, start at pipes, -launch_frontend: Frontend.
|
||||
(line 113)
|
||||
* GPT, _definition: Extras. (line 38)
|
||||
* Group, global in ISO image, -gid: SetWrite. (line 268)
|
||||
* Group, in ISO image, -chgrp: Manip. (line 50)
|
||||
@ -5096,7 +5080,7 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
|
||||
* Program, end without writing, -rollback_end: Scripting. (line 159)
|
||||
* Program, list extra features, -list_extras: Scripting. (line 26)
|
||||
* Program, print help text, -help: Scripting. (line 20)
|
||||
* Program, print help text, -prog_help: Frontend. (line 163)
|
||||
* Program, print help text, -prog_help: Frontend. (line 145)
|
||||
* Program, print message text line, -print_info: Scripting. (line 102)
|
||||
* Program, print result text line, -print: Scripting. (line 99)
|
||||
* Program, print synchronizing text line, -print_mark: Scripting.
|
||||
@ -5104,7 +5088,7 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
|
||||
* Program, print version, -version: Scripting. (line 23)
|
||||
* Program, prompt for enter key, -prompt: Scripting. (line 110)
|
||||
* Program, replace --, -list_delimiter: Scripting. (line 60)
|
||||
* Program, set name, -prog: Frontend. (line 160)
|
||||
* Program, set name, -prog: Frontend. (line 142)
|
||||
* Program, show current settings, -status: Scripting. (line 47)
|
||||
* Program, status history, -status_history_max: Scripting. (line 56)
|
||||
* Program, wait a time span, -sleep: Scripting. (line 114)
|
||||
@ -5210,28 +5194,28 @@ Node: Restore174782
|
||||
Node: Emulation181692
|
||||
Node: Scripting191504
|
||||
Node: Frontend198665
|
||||
Node: Examples207358
|
||||
Node: ExDevices208536
|
||||
Node: ExCreate209195
|
||||
Node: ExDialog210480
|
||||
Node: ExGrowing211745
|
||||
Node: ExModifying212550
|
||||
Node: ExBootable213054
|
||||
Node: ExCharset213606
|
||||
Node: ExPseudo214427
|
||||
Node: ExCdrecord215325
|
||||
Node: ExMkisofs215642
|
||||
Node: ExGrowisofs216982
|
||||
Node: ExException218117
|
||||
Node: ExTime218571
|
||||
Node: ExIncBackup219030
|
||||
Node: ExRestore223022
|
||||
Node: ExRecovery223982
|
||||
Node: Files224552
|
||||
Node: Seealso225851
|
||||
Node: Bugreport226574
|
||||
Node: Legal227155
|
||||
Node: CommandIdx228166
|
||||
Node: ConceptIdx244395
|
||||
Node: Examples206223
|
||||
Node: ExDevices207401
|
||||
Node: ExCreate208060
|
||||
Node: ExDialog209345
|
||||
Node: ExGrowing210610
|
||||
Node: ExModifying211415
|
||||
Node: ExBootable211919
|
||||
Node: ExCharset212471
|
||||
Node: ExPseudo213292
|
||||
Node: ExCdrecord214190
|
||||
Node: ExMkisofs214507
|
||||
Node: ExGrowisofs215847
|
||||
Node: ExException216982
|
||||
Node: ExTime217436
|
||||
Node: ExIncBackup217895
|
||||
Node: ExRestore221887
|
||||
Node: ExRecovery222847
|
||||
Node: Files223417
|
||||
Node: Seealso224716
|
||||
Node: Bugreport225439
|
||||
Node: Legal226020
|
||||
Node: CommandIdx227031
|
||||
Node: ConceptIdx243260
|
||||
|
||||
End Tag Table
|
||||
|
||||
Reference in New Issue
Block a user