libburnia/legacy
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

New command -modesty_on_drive, new -as cdrecord -immed, minbuf=, modesty_on_drive=

Browse Source
This commit is contained in:
Thomas Schmitt
2015-07-31 16:23:08 +00:00
parent a29ed10c14
commit e65ab7648a
16 changed files with 2936 additions and 2722 deletions
Download Patch File Download Diff File Expand all files Collapse all files

66
libisoburn/trunk/xorriso/xorrecord.texi
View File

@ -50,7 +50,7 @@
@c man .\" First parameter, NAME, should be all caps
@c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
@c man .\" other parameters are allowed: see man(7), man(1)
@c man .TH XORRECORD 1 "Version 1.4.1, May 17, 2015"
@c man .TH XORRECORD 1 "Version 1.4.1, Jul 30, 2015"
@c man .\" Please adjust this date whenever revising the manpage.
@c man .\"
@c man .\" Some roff macros, for reference:
@ -196,8 +196,8 @@ device file.
On Solaris, the user needs r-permission and privilege "sys_devices",
which is usually gained by running @command{xorrecord} via command pfexec.
@*
These permissions resp. privileges are needed already for listing a drive.
So it might be necessary to get the overview as superuser resp. via pfexec.
These permissions or privileges are needed already for listing a drive.
So it might be necessary to get the overview as superuser or via pfexec.
@*
@command{xorrecord} does not perform cdrecord option -scanbus and does
not accept the addresses of form Bus,Target,Lun which are told by -scanbus.
@ -228,7 +228,7 @@ to generic xorriso command mode. See @strong{man xorriso} for its description.
Other than in xorriso command mode, the sequence of the cdrecord emulation
options does not matter.
All pending actions get performed in a fixed sequence before the program
run ends resp. before cdrecord emulation ends.
run ends or before cdrecord emulation ends.
@c man .SS
@node Options, Examples, Xorriso, Top
@chapter Options
@ -648,6 +648,20 @@ MMC drives usually activate their own idea of speed and take
the speed value given by the burn program only as a hint
for their own decision.
@c man .TP
@item minbuf=percentage
@kindex minbuf= keep drive buffer hungry
@cindex Write, drive buffer, minbuf=
Equivalent to:
@*
modesty_on_drive=<percentage>
@c man .TP
@item -immed
@kindex -immed keep drive buffer hungry
@cindex Write, drive buffer, -immed
Equivalent to:
@*
modesty_on_drive=75
@c man .TP
@item -eject
@kindex -eject finally eject drive tray
@cindex Eject, the tray, -eject
@ -679,7 +693,7 @@ Afterwards end emulation without performing any drive operation.
@cindex Verbosity, increase, -v
Increase program verbosity by one level. There are four verbosity levels
from nearly silent to debugging verbosity. The both highest levels can
be enabled by repeated -v or by -vv resp. -vvv.
be enabled by repeated -v or by -vv or by -vvv.
@c man .TP
@item -V
@kindex -V log SCSI command transactions to stderr
@ -779,6 +793,46 @@ size. A number of 64 KB may improve throughput with bus systems which
show latency problems. The default depends on media type, option
stream_recording=, and on compile time options.
@c man .TP
@item modesty_on_drive=parameter[:parameters]
@kindex -modesty_on_drive keep drive buffer hungry
@cindex Write, drive buffer, modesty_on_drive=
Control whether the drive buffer shall be kept from getting completely filled.
Parameter "on" (or "1") keeps the program from trying to write to the burner
drive while its buffer is in danger to be filled over a given limit.
If this filling is exceeded then the program will wait until the filling
reaches a given low percentage value.
@*
This can ease the load on operating system and drive controller and thus help
with achieving better input bandwidth if disk and burner are not on independent
controllers (like hda and hdb). It may also help with simultaneous burns on
different burners with Linux kernels like 3.16. On the other hand it increases
the risk of buffer underflow and thus reduced write speed.
@*
Some burners are not suitable because they
report buffer fill with granularity too coarse in size or time,
or expect their buffer to be filled to the top before they go to full speed.
@*
Parameters "off" or "0" disable this feature.
@*
The threshhold for beginning to wait is given by parameter "max_percent=".
Parameter "min_percent=" defines the threshhold for resuming transmission.
Percentages are permissible in the range of 25 to 100. Numbers in this
range without a prepended name are interpreted as "on:min_percent=".
@*
E.g.: modesty_on_drive=75
@*
The optimal values depend on the buffer behavior of the drive.
@*
There are also timing parameters "timeout_sec=", "min_usec=", "max_usec=".
Read the description of burn_drive_set_buffer_waiting() in libburn.h,
before setting them to non-default values.
@*
Parameters, which are not mentioned with a modesty_on_drive= option,
stay unchanged.
Default is:
@*
modesty_on_drive=off:min_percent=65:max_percent=95
@c man .TP
@item write_start_address=value
@kindex write_start_address= set block address for write start
@cindex Write start address, set, write_start_address=
@ -1057,7 +1111,7 @@ If more privacy is desired, mail to @email{scdbackup@@gmx.net}.
@*
@sp 1
Please describe what you expect @command{xorriso} to do,
the program arguments resp. commands by which you tried to achieve it,
the program arguments or dialog commands by which you tried to achieve it,
the messages of @command{xorriso}, and the undesirable outcome of your
program run.
@*