/usr/share/doc/stilts/sun256/stilts-flags.html is in stilts-doc 3.1.2-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 | <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" type="text/css" href="sun-style.css">
<title>Stilts flags</title>
</head>
<body>
<hr>
<a href="task-name.html">Next</a> <a href="stilts-cmd.html">Previous</a> <a href="stilts-cmd.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="task-name.html">Task Names</a><br>
<b>Up: </b><a href="stilts-cmd.html">The stilts command</a><br>
<b>Previous: </b><a href="stilts-cmd.html">The stilts command</a><br>
<hr>
<h3><a name="stilts-flags">2.1 Stilts flags</a></h3>
<p>Some flags are common to all the tasks in the STILTS package,
and these are specified after the <code>stilts</code> invocation itself
and before the task name. They generally have the same effect
regardless of which task is running. These generic flags are as
follows:
<dl>
<dt><strong><code>-help</code></strong></dt>
<dd>Prints a usage message for the <code>stilts</code> command
itself and exits. The message contains a listing of all the
known tasks.
</dd>
<dt><strong><code>-version</code></strong></dt>
<dd>Prints the STILTS version number and exits.
</dd>
<dt><strong><code>-verbose</code></strong></dt>
<dd>Causes more verbose information to be written during operation.
Specifically, what this does is to boost the logging level by
one notch. It may be specified multiple times to increase verbosity
further.
</dd>
<dt><strong><code>-allowunused</code></strong></dt>
<dd>Causes unused parameter settings on the command line to be tolerated.
Normally, any unused parameters on the command line cause a usage
message to be output and the command to fail, on the assumption
that if you've supplied a parameter setting that's not doing anything
it is probably a mistake and you should be given a chance to correct it.
But if this flag is set, you just get a warning through the logging
system about any unused parameters, and the command is executed as
if they weren't there.
</dd>
<dt><strong><code>-prompt</code></strong></dt>
<dd>Most of the STILTS commands have a number of parameters which
will assume sensible defaults if you do not give them explicit
values on the command line. If you use the <code>-prompt</code> flag,
then you will be prompted for every parameter you have not
explicitly specified to give you an opportunity to enter a value
other than the default.
</dd>
<dt><strong><code>-bench</code></strong></dt>
<dd>Outputs the elapsed time taken by the task to standard error on
successful completion.
</dd>
<dt><strong><code>-debug</code></strong></dt>
<dd>Sets up output suitable for debugging. The most visible consequence
of this is that if an error occurs then a full stacktrace is output,
rather than just a user-friendly report.
</dd>
<dt><strong><code>-batch</code></strong></dt>
<dd>Some parameters will prompt you for their values, even if they
offer legal defaults. If you use the <code>-batch</code> flag,
then you won't be prompted at all.
</dd>
<dt><strong><code>-memory</code></strong></dt>
<dd>Encourages the command to use java heap memory for caching
large amounts of data rather than using temporary disk files.
The default is to use memory for small tables, and disk for large ones.
This flag is in most cases equivalent to specifying the system
property <code>-Dstartable.storage=memory</code>.
</dd>
<dt><strong><code>-disk</code></strong></dt>
<dd>Encourages the command to use temporary files on disk for caching
table data.
The default is to use memory for small tables, and disk for large ones.
Using this flag may help if you are running out of memory.
This flag is in most cases equivalent to specifying the system
property <code>-Dstartable.storage=disk</code>.
</dd>
<dt><strong><code>-memgui</code></strong></dt>
<dd>Displays a graphical window while the command is running which
summarises used and available heap memory.
May be useful for profiling or understanding resource constraints.
</dd>
<dt><strong><code>-checkversion <vers></code></strong></dt>
<dd>Requires that the version is exactly as given by the string
<code><vers></code>. If it is not, STILTS will exit with
an error. This can be useful when executing in certain controlled
environments to ensure that the correct version of the application
is being picked up.
</dd>
<dt><strong><code>-stdout <file></code></strong></dt>
<dd>Sends all normal output from the run to the given file.
By default this goes to the standard output stream.
Supplying an empty string or "<code>-</code>" for <code><file></code>
will restore this default behaviour.
</dd>
<dt><strong><code>-stderr <file></code></strong></dt>
<dd>Sends all error output from the run to the given file.
By default this goes to the standard error stream.
Supplying an empty string or "<code>-</code>" for <code><file></code>
will restore this default behaviour.
</dd>
</dl>
</p>
<p>If you are submitting an error report, please include the result of
running <code>stilts -version</code> and the output of the troublesome
command with the <code>-debug</code> flag specified.
</p>
<hr><a href="task-name.html">Next</a> <a href="stilts-cmd.html">Previous</a> <a href="stilts-cmd.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="task-name.html">Task Names</a><br>
<b>Up: </b><a href="stilts-cmd.html">The stilts command</a><br>
<b>Previous: </b><a href="stilts-cmd.html">The stilts command</a><br>
<hr><i>STILTS - Starlink Tables Infrastructure Library Tool Set<br>Starlink User Note256<br>STILTS web page:
<a href="http://www.starlink.ac.uk/stilts/">http://www.starlink.ac.uk/stilts/</a><br>Author email:
<a href="mailto:m.b.taylor@bristol.ac.uk">m.b.taylor@bristol.ac.uk</a><br>Mailing list:
<a href="mailto:topcat-user@jiscmail.ac.uk">topcat-user@jiscmail.ac.uk</a><br></i></body>
</html>
|