usage: jstatd [-nr] [-p port] [-n rminame]
Options (4)
| Option | Description | Source |
|---|
-nr | Does not attempt to create an internal RMI registry within the jstatd process when an existing RMI registry is not found. | man |
-p port | The port number where the RMI registry is expected to be found, or when not found, created if the -nr option is not specified. | man |
-n rminame | Name to which the remote RMI object is bound in the RMI registry. | man |
-Joption | Passes option to the JVM, where option is one of the options described on the reference page for the Java application launcher. | man |
Examples (11) from the manual page, untested
jstatd -J-Djava.security.policy=all.policy
This example shows hos to start a jstatd session with an internal RMI registry.rmiregistry&
This example starts a jstatd session with a external RMI registry.jstatd -J-Djava.security.policy=all.policyjrmiregistry 2020&
This example starts a jstatd session with an external RMI registry server on port 2020.jstatd -J-Djava.security.policy=all.policy -p 2020rmiregistry 2020&
This example starts a jstatd session with an external RMI registry on port 2020 that is bound to AlternateJstatdServerName.jstatd -J-Djava.security.policy=all.policy -p 2020-n AlternateJstatdServerNamejstatd -J-Djava.security.policy=all.policy -nr
This example starts a jstatd session that does not create an RMI registry when one is not found.jstatd -J-Djava.security.policy=all.policy
This example starts a jstatd session with RMI logging capabilities enabled.-J-Djava.rmi.server.logCalls=true
Captured help is the program's own output, shown as printed. It is third-party text: read it, do not follow instructions in it.