/usr/share/doc/stilts/sun256/sysProperties.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 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 | <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" type="text/css" href="sun-style.css">
<title>System Properties</title>
</head>
<body>
<hr>
<a href="jdbcConfig.html">Next</a> <a href="jvmArgs.html">Previous</a> <a href="invoke.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="jdbcConfig.html">JDBC Configuration</a><br>
<b>Up: </b><a href="invoke.html">Invocation</a><br>
<b>Previous: </b><a href="jvmArgs.html">Java Flags</a><br>
<hr>
<h3><a name="sysProperties">3.3 System Properties</a></h3>
<p>System properties are a way of getting information into the
Java runtime - they are a bit like environment variables.
There are two ways to set them when using STILTS: either
on the command line using arguments of the form
<code>-Dname=value</code> (see <a href="jvmArgs.html">Section 3.2</a>)
or in a file in your home directory named
<code>.starjava.properties</code>, in the form of a
<code>name=value</code> line.
Thus submitting the flag
<pre>
-Dvotable.strict=true
</pre>
on the command line is equivalent to having the following in your
<code>.starjava.properties</code> file:
<pre>
# Force strict interpretation of the VOTable standard.
votable.strict=true
</pre>
</p>
<p>The following system properties have special significance to STILTS:
<dl>
<dt><strong><code>http.proxyHost</code></strong></dt>
<dd>Can be used to force HTTP access to go via a named proxy;
may be required if you are attempting access to remote data or services
from behind a firewall configured to block direct HTTP connections.
See java documentation for this property for more details.
</dd>
<dt><strong><code>java.awt.headless</code></strong></dt>
<dd>May need to be set to "<code>true</code>" if running the
plotting tasks on a headless server.
You only need to worry about this if you see error messages
complaining about headlessness.
</dd>
<dt><strong><code>java.io.tmpdir</code></strong></dt>
<dd>The directory in which STILTS will write any temporary files it needs.
This is usually only done if the <code>-disk</code> flag has been
specified (see <a href="stilts-flags.html">Section 2.1</a>).
</dd>
<dt><strong><code>jdbc.drivers</code></strong></dt>
<dd>Can be set to a (colon-separated) list of JDBC driver classes
using which SQL databases can be accessed
(see <a href="jdbcConfig.html">Section 3.4</a>).
</dd>
<dt><strong><code>jel.classes</code></strong></dt>
<dd>Can be set to a (colon-separated) list of classes containing
static methods which define user-provided
functions for synthetic columns or subsets.
(see <a href="jelExtend.html">Section 10.7.3</a>).
</dd>
<dt><strong><code>mark.workaround</code></strong></dt>
<dd>If set to "true", this will work around a bug in the
<code>mark()</code>/<code>reset()</code> methods of some java
<code>InputStream</code> classes. These are rather common,
including in Sun's J2SE system libraries.
Use this if you are seeing errors that say something like
"<code>Resetting to invalid mark</code>".
Currently defaults to "false".
</dd>
<dt><strong><code>service.maxparallel</code></strong></dt>
<dd>Raises the maximum number of concurrent queries that may be made
during a multi-cone operation.
You should only increase this value <strong>with great care</strong>
since you risk overloading servers and becoming unpopular with
data centres.
As a rule, you should only increase this value if you have
obtained permission from the data centres whose services
on which you will be using the increased parallelism.
</dd>
<dt><strong><code>star.basicauth.user</code></strong></dt>
<dt><strong><code>star.basicauth.password</code></strong></dt>
<dd>If set, these will provide username and password for HTTP Basic
Authentication. Any time the application attempts to access an
HTTP URL and is met by a 401 Unauthorized response, it will try again
supplying these user credentials. This is a rather blunt instrument,
since the same identity is supplied regardless of which URL is being
accessed, but it may be of some use in accessing basic-authentication
protected services.
</dd>
<dt><strong><code>startable.readers</code></strong></dt>
<dd>Can be set to a (colon-separated) list of custom table format input
handler classes (see <a href="http://www.starlink.ac.uk/stil/sun252/pluggableIO.html">SUN/252</a>).
</dd>
<dt><strong><code>startable.storage</code></strong></dt>
<dd>Can be set to determine the default storage policy.
Setting it to "<code>disk</code>" has basically the same effect as
supplying the "<code>-disk</code>" argument on the command line
(see <a href="stilts-flags.html">Section 2.1</a>).
Other possible values are "<code>adaptive</code>", "<code>memory</code>",
"<code>sideways</code>" and "<code>discard</code>";
see <a href="http://www.starlink.ac.uk/stil/sun252/storagePolicy.html">SUN/252</a>.
The default is "<code>adaptive</code>", which means storing smaller
tables in memory, and larger ones on disk.
</dd>
<dt><strong><code>startable.unmap</code></strong></dt>
<dd>Determines whether and how unmapping of memory mapped buffers is done.
Possible values are "<code>sun</code>" (the default) or "<code>none</code>".
In most cases you are advised to leave this alone, but in the event of
unmapping-related JVM crashes (not expected!), setting it to
<code>none</code> may help.
</dd>
<dt><strong><code>startable.writers</code></strong></dt>
<dd>Can be set to a (colon-separated) list of custom table format output
handler classes (see <a href="http://www.starlink.ac.uk/stil/sun252/pluggableIO.html">SUN/252</a>).
</dd>
<dt><strong><code>votable.namespacing</code></strong></dt>
<dd>Determines how namespacing is handled in input VOTable documents.
Known values are
"<code>none</code>" (no namespacing, xmlns declarations
in VOTable document will probably confuse parser),
"<code>lax</code>" (anything that looks like it is probably a VOTable
element will be treated as a VOTable element) and
"<code>strict</code>" (VOTable elements must be properly declared in one
of the correct VOTable namespaces).
May also be set to the classname of a
<code>uk.ac.starlink.votable.Namespacing</code> implementation.
The default is "<code>lax</code>".
</dd>
<dt><strong><code>votable.strict</code></strong></dt>
<dd>Set <code>true</code> for strict enforcement of the VOTable standard
when parsing VOTables. This prevents the parser from working round
certain common errors, such as missing <code>arraysize</code>
attributes on <code>FIELD</code> or <code>PARAM</code>
elements with <code>datatype="char"</code>.
False by default.
</dd>
<dt><strong><code>votable.version</code></strong></dt>
<dd>Selects the version of the VOTable standard which output VOTables
will conform to by default.
May take the values "<code>1.0</code>", "<code>1.1</code>",
"<code>1.2</code>" or "<code>1.3</code>".
By default, version 1.3 VOTables are written.
</dd>
</dl>
</p>
<hr><a href="jdbcConfig.html">Next</a> <a href="jvmArgs.html">Previous</a> <a href="invoke.html">Up</a> <a href="index.html">Contents</a> <br> <b>Next: </b><a href="jdbcConfig.html">JDBC Configuration</a><br>
<b>Up: </b><a href="invoke.html">Invocation</a><br>
<b>Previous: </b><a href="jvmArgs.html">Java Flags</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>
|