< prev index next >
src/java.rmi/share/man/rmid.1
Print this page
@@ -1,7 +1,6 @@
-'\" t
-.\" Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
+.\" Copyright (c) 1994, 2019, Oracle and/or its affiliates. All rights reserved.
.\" DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
.\"
.\" This code is free software; you can redistribute it and/or modify it
.\" under the terms of the GNU General Public License version 2 only, as
.\" published by the Free Software Foundation.
@@ -18,297 +17,394 @@
.\"
.\" Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
.\" or visit www.oracle.com if you need additional information or have any
.\" questions.
.\"
-.\" Arch: generic
-.\" Software: JDK 8
-.\" Date: 21 November 2013
-.\" SectDesc: Remote Method Invocation (RMI) Tools
-.\" Title: rmid.1
+.\" Automatically generated by Pandoc 2.3.1
.\"
-.if n .pl 99999
-.TH rmid 1 "21 November 2013" "JDK 8" "Remote Method Invocation (RMI) Tools"
-.\" -----------------------------------------------------------------
-.\" * Define some portability stuff
-.\" -----------------------------------------------------------------
-.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-.\" http://bugs.debian.org/507673
-.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
-.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-.ie \n(.g .ds Aq \(aq
-.el .ds Aq '
-.\" -----------------------------------------------------------------
-.\" * set default formatting
-.\" -----------------------------------------------------------------
-.\" disable hyphenation
-.nh
-.\" disable justification (adjust text to left margin only)
-.ad l
-.\" -----------------------------------------------------------------
-.\" * MAIN CONTENT STARTS HERE *
-.\" -----------------------------------------------------------------
-
+.TH "RMID" "1" "2018" "JDK 13" "JDK Commands"
+.hy
.SH NAME
-rmid \- Starts the activation system daemon that enables objects to be registered and activated in a Java Virtual Machine (JVM)\&.
+.PP
+rmid \- start the activation system daemon that enables objects to be
+registered and activated in a Java Virtual Machine (JVM)
.SH SYNOPSIS
-.sp
-.nf
-
-\fBrmid\fR [\fIoptions\fR]
-.fi
-.sp
+.PP
+\f[CB]rmid\f[R] [\f[I]options\f[R]]
.TP
-\fIoptions\fR
-The command-line options\&. See Options\&.
+.B \f[I]options\f[R]
+This represent the command\-line options for the \f[CB]rmid\f[R] command.
+See \f[B]Options for rmid\f[R].
+.RS
+.RE
.SH DESCRIPTION
-The \f3rmid\fR command starts the activation system daemon\&. The activation system daemon must be started before activatable objects can be either registered with the activation system or activated in a JVM\&. For details on how to write programs that use activatable objects, the \fIUsing Activation\fR tutorial at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/rmi/activation/overview\&.html
.PP
-Start the daemon by executing the \f3rmid\fR command and specifying a security policy file, as follows:
-.sp
-.nf
-\f3rmid \-J\-Djava\&.security\&.policy=rmid\&.policy\fP
-.fi
-.nf
-\f3\fP
-.fi
-.sp
-When you run Oracle\(cqs implementation of the \f3rmid\fR command, by default you must specify a security policy file so that the \f3rmid\fR command can verify whether or not the information in each \f3ActivationGroupDesc\fR is allowed to be used to start a JVM for an activation group\&. Specifically, the command and options specified by the \f3CommandEnvironment\fR and any properties passed to an \f3ActivationGroupDesc\fR constructor must now be explicitly allowed in the security policy file for the \f3rmid\fR command\&. The value of the \f3sun\&.rmi\&.activation\&.execPolicy\fR property dictates the policy that the \f3rmid\fR command uses to determine whether or not the information in an \f3ActivationGroupDesc\fR can be used to start a JVM for an activation group\&. For more information see the description of the -J-Dsun\&.rmi\&.activation\&.execPolicy=policy option\&.
+The \f[CB]rmid\f[R] command starts the activation system daemon.
+The activation system daemon must be started before objects that can be
+activated are either registered with the activation system or activated
+in a JVM.
.PP
-Executing the \f3rmid\fR command starts the Activator and an internal registry on the default port1098 and binds an \f3ActivationSystem\fR to the name \f3java\&.rmi\&.activation\&.ActivationSystem\fR in this internal registry\&.
+Start the daemon by executing the \f[CB]rmid\f[R] command and specifying a
+security policy file, as follows:
+.RS
.PP
-To specify an alternate port for the registry, you must specify the \f3-port\fR option when you execute the \f3rmid\fR command\&. For example, the following command starts the activation system daemon and a registry on the registry\&'s default port, 1099\&.
-.sp
-.nf
-\f3rmid \-J\-Djava\&.security\&.policy=rmid\&.policy \-port 1099\fP
-.fi
-.nf
-\f3\fP
-.fi
-.sp
-.SH START\ RMID\ ON\ DEMAND
-An alternative to starting \f3rmid\fR from the command line is to configure \f3inetd\fR (Oracle Solaris) or \f3xinetd\fR (Linux) to start \f3rmid\fR on demand\&.
-.PP
-When RMID starts, it attempts to obtain an inherited channel (inherited from \f3inetd\fR/\f3xinetd\fR) by calling the \f3System\&.inheritedChannel\fR method\&. If the inherited channel is null or not an instance of \f3java\&.nio\&.channels\&.ServerSocketChannel\fR, then RMID assumes that it was not started by \f3inetd\fR/\f3xinetd\fR, and it starts as previously described\&.
-.PP
-If the inherited channel is a \f3ServerSocketChannel\fR instance, then RMID uses the \f3java\&.net\&.ServerSocket\fR obtained from the \f3ServerSocketChannel\fR as the server socket that accepts requests for the remote objects it exports: The registry in which the \f3java\&.rmi\&.activation\&.ActivationSystem\fR is bound and the \f3java\&.rmi\&.activation\&.Activator\fR remote object\&. In this mode, RMID behaves the same as when it is started from the command line, except in the following cases:
-.TP 0.2i
-\(bu
-Output printed to \f3System\&.err\fR is redirected to a file\&. This file is located in the directory specified by the \f3java\&.io\&.tmpdir\fR system property (typically \f3/var/tmp\fR or \f3/tmp\fR) with the prefix \f3rmid-err\fR and the suffix \f3tmp\fR\&.
-.TP 0.2i
-\(bu
-The \f3-port\fR option is not allowed\&. If this option is specified, then RMID exits with an error message\&.
-.TP 0.2i
-\(bu
-The \f3-log\fR option is required\&. If this option is not specified, then RMID exits with an error message
+\f[CB]rmid\ \-J\-Djava.security.policy=rmid.policy\f[R]
+.RE
+.PP
+When you run Oracle\[aq]s implementation of the \f[CB]rmid\f[R] command,
+by default you must specify a security policy file so that the
+\f[CB]rmid\f[R] command can verify whether or not the information in each
+\f[CB]ActivationGroupDesc\f[R] is allowed to be used to start a JVM for an
+activation group.
+Specifically, the command and options specified by the
+\f[CB]CommandEnvironment\f[R] and any properties passed to an
+\f[CB]ActivationGroupDesc\f[R] constructor must now be explicitly allowed
+in the security policy file for the \f[CB]rmid\f[R] command.
+The value of the \f[CB]sun.rmi.activation.execPolicy\f[R] property
+dictates the policy that the \f[CB]rmid\f[R] command uses to determine
+whether or not the information in an \f[CB]ActivationGroupDesc\f[R] can be
+used to start a JVM for an activation group.
+For more information see the description of the
+\f[CB]\-J\-Dsun.rmi.activation.execPolicy=policy\f[R] option.
+.PP
+Executing the \f[CB]rmid\f[R] command starts the \f[CB]Activator\f[R] and an
+internal registry on the default port 1098 and binds an
+\f[CB]ActivationSystem\f[R] to the name
+\f[CB]java.rmi.activation.ActivationSystem\f[R] in this internal registry.
+.PP
+To specify an alternate port for the registry, you must specify the
+\f[CB]\-port\f[R] option when you execute the \f[CB]rmid\f[R] command.
+For example, the following command starts the activation system daemon
+and a registry on the registry\[aq]s default port, 1099.
+.RS
+.PP
+\f[CB]rmid\ \-J\-Djava.security.policy=rmid.policy\ \-port\ 1099\f[R]
+.RE
+.SH START RMID ON DEMAND (ORACLE SOLARIS AND LINUX ONLY)
.PP
-See the man pages for \f3inetd\fR (Oracle Solaris) or \f3xinetd\fR (Linux) for details on how to configure services to be started on demand\&.
-.SH OPTIONS
+An alternative to starting \f[CB]rmid\f[R] from the command line is to
+configure \f[CB]inetd\f[R] (Oracle Solaris) or \f[CB]xinetd\f[R] (Linux) to
+start \f[CB]rmid\f[R] on demand.
+.PP
+When RMID starts, it attempts to obtain an inherited channel (inherited
+from \f[CB]inetd\f[R]/\f[CB]xinetd\f[R]) by calling the
+\f[CB]System.inheritedChannel\f[R] method.
+If the inherited channel is null or not an instance of
+\f[CB]java.nio.channels.ServerSocketChannel\f[R], then RMID assumes that
+it wasn\[aq]t started by \f[CB]inetd\f[R]/\f[CB]xinetd\f[R], and it starts
+as previously described.
+.PP
+If the inherited channel is a \f[CB]ServerSocketChannel\f[R] instance,
+then RMID uses the \f[CB]java.net.ServerSocket\f[R] obtained from the
+\f[CB]ServerSocketChannel\f[R] as the server socket that accepts requests
+for the remote objects it exports: The registry in which the
+\f[CB]java.rmi.activation.ActivationSystem\f[R] is bound and the
+\f[CB]java.rmi.activation.Activator\f[R] remote object.
+In this mode, RMID behaves the same as when it is started from the
+command line, except in the following cases:
+.IP \[bu] 2
+Output printed to \f[CB]System.err\f[R] is redirected to a file.
+This file is located in the directory specified by the
+\f[CB]java.io.tmpdir\f[R] system property (typically \f[CB]/var/tmp\f[R] or
+\f[CB]/tmp\f[R]) with the prefix \f[CB]rmid\-err\f[R] and the suffix
+\f[CB]tmp\f[R].
+.IP \[bu] 2
+The \f[CB]\-port\f[R] option isn\[aq]t allowed.
+If this option is specified, then RMID exits with an error message.
+.IP \[bu] 2
+The \f[CB]\-log\f[R] option is required.
+If this option isn\[aq]t specified, then RMID exits with an error
+message
+.SH OPTIONS FOR RMID
.TP
--C\fIoption\fR
-.br
-Specifies an option that is passed as a command-line argument to each child process (activation group) of the \f3rmid\fR command when that process is created\&. For example, you could pass a property to each virtual machine spawned by the activation system daemon:
-.sp
-.nf
-\f3rmid \-C\-Dsome\&.property=value\fP
-.fi
-.nf
-\f3\fP
-.fi
-.sp
-
-
-This ability to pass command-line arguments to child processes can be useful for debugging\&. For example, the following command enables server-call logging in all child JVMs\&.
-.sp
-.nf
-\f3rmid \-C\-Djava\&.rmi\&.server\&.logCalls=true\fP
-.fi
-.nf
-\f3\fP
-.fi
-.sp
-
+.B \f[CB]\-C\f[R]\f[I]option\f[R]
+Specifies an option that\[aq]s passed as a command\-line argument to
+each child process (activation group) of the \f[CB]rmid\f[R] command when
+that process is created.
+For example, you could pass a property to each virtual machine spawned
+by the activation system daemon:
+.RS
+.RS
+.PP
+\f[CB]rmid\ \-C\-Dsome.property=value\f[R]
+.RE
+.PP
+This ability to pass command\-line arguments to child processes can be
+useful for debugging.
+For example, the following command enables server\-call logging in all
+child JVMs.
+.RS
+.PP
+\f[CB]rmid\ \-C\-Djava.rmi.server.logCalls=true\f[R]
+.RE
+.RE
.TP
--J\fIoption\fR
-.br
-Specifies an option that is passed to the Java interpreter running RMID\&. For example, to specify that the \f3rmid\fR command use a policy file named \f3rmid\&.policy\fR, the \f3-J\fR option can be used to define the \f3java\&.security\&.policy\fR property on the \f3rmid\fR command line, for example:
-.sp
-.nf
-\f3rmid \-J\-Djava\&.security\&.policy\-rmid\&.policy\fP
-.fi
-.nf
-\f3\fP
-.fi
-.sp
-
+.B \f[CB]\-J\f[R]\f[I]option\f[R]
+Specifies an option that\[aq]s passed to the Java interpreter running
+RMID command.
+For example, to specify that the \f[CB]rmid\f[R] command use a policy file
+named \f[CB]rmid.policy\f[R], the \f[CB]\-J\f[R] option can be used to
+define the \f[CB]java.security.policy\f[R] property on the \f[CB]rmid\f[R]
+command line, for example:
+.RS
+.RS
+.PP
+\f[CB]rmid\ \-J\-Djava.security.policy\-rmid.policy\f[R]
+.RE
+.RE
.TP
--J-Dsun\&.rmi\&.activation\&.execPolicy=\fIpolicy\fR
-.br
-Specifies the policy that RMID employs to check commands and command-line options used to start the JVM in which an activation group runs\&. Please note that this option exists only in Oracle\&'s implementation of the Java RMI activation daemon\&. If this property is not specified on the command line, then the result is the same as though \f3-J-Dsun\&.rmi\&.activation\&.execPolicy=default\fR were specified\&. The possible values of \f3policy\fR can be \f3default\fR, \f3policyClassName\fR, or \f3none\fR\&.
-.RS
-.TP 0.2i
-\(bu
-default
-
-The \f3default\fR or unspecified value \f3execPolicy\fR allows the \f3rmid\fR command to execute commands with specific command-line options only when the \f3rmid\fR command was granted permission to execute those commands and options in the security policy file that the \f3rmid\fR command uses\&. Only the default activation group implementation can be used with the default execution policy\&.
-
-The \f3rmid\fR command starts a JVM for an activation group with the information in the group\&'s registered activation group descriptor, an \f3ActivationGroupDesc\fR\&. The group descriptor specifies an optional \f3ActivationGroupDesc\&.CommandEnvironment\fR that includes the command to execute to start the activation group and any command-line options to be added to the command line\&. By default, the \f3rmid\fR command uses the \f3java\fR command found in \f3java\&.home\fR\&. The group descriptor also contains properties overrides that are added to the command line as options defined as: \f3-D<property>=<value>\fR\&.The \f3com\&.sun\&.rmi\&.rmid\&.ExecPermission\fR permission grants the \f3rmid\fR command permission to execute a command that is specified in the group descriptor\&'s \f3CommandEnvironment\fR to start an activation group\&. The \f3com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fR permission enables the \f3rmid\fR command to use command-line options, specified as properties overrides in the group descriptor or as options in the \f3CommandEnvironment\fR when starting the activation group\&.When granting the \f3rmid\fR command permission to execute various commands and options, the permissions \f3ExecPermission\fR and \f3ExecOptionPermission\fR must be granted to all code sources\&.
-
-\fIExecPermission\fR
-
-The \f3ExecPermission\fR class represents permission for the \f3rmid\fR command to execute a specific command to start an activation group\&.
-
-\fISyntax\fR: The name of an \f3ExecPermission\fR is the path name of a command to grant the \f3rmid\fR command permission to execute\&. A path name that ends in a slash (/) and an asterisk (*) indicates that all of the files contained in that directory where slash is the file-separator character, \f3File\&.separatorChar\fR\&. A path name that ends in a slash (/) and a minus sign (-) indicates all files and subdirectories contained in that directory (recursively)\&. A path name that consists of the special token \f3<<ALL FILES>>\fR matches any file\&.
-
-A path name that consists of an asterisk (*) indicates all the files in the current directory\&. A path name that consists of a minus sign (-) indicates all the files in the current directory and (recursively) all files and subdirectories contained in the current directory\&.
-
-\fIExecOptionPermission\fR
-
-The \f3ExecOptionPermission\fR class represents permission for the \f3rmid\fR command to use a specific command-line option when starting an activation group\&. The name of an \f3ExecOptionPermission\fR is the value of a command-line option\&.
-
-\fISyntax\fR: Options support a limited wild card scheme\&. An asterisk signifies a wild card match, and it can appear as the option name itself (matches any option), or an asterisk (*) can appear at the end of the option name only when the asterisk (*) follows a dot (\&.) or an equals sign (=)\&.
-
-For example: \f3*\fR or \f3-Dmydir\&.*\fR or \f3-Da\&.b\&.c=*\fR is valid, but \f3*mydir\fR or \f3-Da*b\fR or \f3ab*\fR is not\&.
-
-\fIPolicy file for rmid\fR
-
-When you grant the \f3rmid\fR command permission to execute various commands and options, the permissions \f3ExecPermission\fR and \f3ExecOptionPermission\fR must be granted to all code sources (universally)\&. It is safe to grant these permissions universally because only the \f3rmid\fR command checks these permissions\&.
-
-An example policy file that grants various execute permissions to the \f3rmid\fR command is:
-.sp
-.nf
-\f3grant {\fP
-.fi
-.nf
-\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecPermission\fP
-.fi
-.nf
-\f3 "/files/apps/java/jdk1\&.7\&.0/solaris/bin/java";\fP
-.fi
-.nf
-\f3\fP
-.fi
-.nf
-\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecPermission\fP
-.fi
-.nf
-\f3 "/files/apps/rmidcmds/*";\fP
-.fi
-.nf
-\f3\fP
-.fi
-.nf
-\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fP
-.fi
-.nf
-\f3 "\-Djava\&.security\&.policy=/files/policies/group\&.policy";\fP
-.fi
-.nf
-\f3\fP
-.fi
-.nf
-\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fP
-.fi
-.nf
-\f3 "\-Djava\&.security\&.debug=*";\fP
-.fi
-.nf
-\f3\fP
-.fi
-.nf
-\f3 permission com\&.sun\&.rmi\&.rmid\&.ExecOptionPermission\fP
-.fi
-.nf
-\f3 "\-Dsun\&.rmi\&.*";\fP
-.fi
-.nf
-\f3};\fP
-.fi
-.nf
-\f3\fP
-.fi
-.sp
-
-
-The first permission granted allows the \f3rmid\fR tcommand o execute the 1\&.7\&.0 release of the \f3java\fR command, specified by its explicit path name\&. By default, the version of the \f3java\fR command found in \f3java\&.home\fR is used (the same one that the \f3rmid\fR command uses), and does not need to be specified in the policy file\&. The second permission allows the \f3rmid\fR command to execute any command in the directory \f3/files/apps/rmidcmds\fR\&.
-
-The third permission granted, an \f3ExecOptionPermission\fR, allows the \f3rmid\fR command to start an activation group that defines the security policy file to be \f3/files/policies/group\&.policy\fR\&. The next permission allows the \f3java\&.security\&.debug property\fR to be used by an activation group\&. The last permission allows any property in the \f3sun\&.rmi property\fR name hierarchy to be used by activation groups\&.
-
-To start the \f3rmid\fR command with a policy file, the \f3java\&.security\&.policy\fR property needs to be specified on the \f3rmid\fR command line, for example:
-
-\f3rmid -J-Djava\&.security\&.policy=rmid\&.policy\fR\&.
-.TP 0.2i
-\(bu
-<policyClassName>
-
-If the default behavior is not flexible enough, then an administrator can provide, when starting the \f3rmid\fR command, the name of a class whose \f3checkExecCommand\fR method is executed to check commands to be executed by the \f3rmid\fR command\&.
-
-The \f3policyClassName\fR specifies a public class with a public, no-argument constructor and an implementation of the following \f3checkExecCommand\fR method:
-.sp
-.nf
-\f3 public void checkExecCommand(ActivationGroupDesc desc, String[] command)\fP
+.B \f[CB]\-J\-Dsun.rmi.activation.execPolicy=\f[R]\f[I]policy\f[R]
+Specifies the policy that the RMID command employs to check commands and
+command\-line options used to start the JVM in which an activation group
+runs.
+This option exists only in Oracle\[aq]s implementation of the Java RMI
+activation daemon.
+If this property isn\[aq]t specified on the command line, then the
+result is the same as though
+\f[CB]\-J\-Dsun.rmi.activation.execPolicy=default\f[R] were specified.
+.RS
+.PP
+The possible values of \f[I]policy\f[R] can be \f[CB]default\f[R],
+\f[I]policyClassName\f[R], or \f[CB]none\f[R].
+.IP \[bu] 2
+\f[CB]default\f[R]
+.RS 2
+.PP
+The \f[CB]default\f[R] or unspecified value \f[CB]execPolicy\f[R] allows the
+\f[CB]rmid\f[R] command to execute commands with specific command\-line
+options only when the \f[CB]rmid\f[R] command was granted permission to
+execute those commands and options in the security policy file that the
+\f[CB]rmid\f[R] command uses.
+Only the default activation group implementation can be used with the
+default execution policy.
+.PP
+The \f[CB]rmid\f[R] command starts a JVM for an activation group with the
+information in the group\[aq]s registered activation group descriptor,
+\f[CB]ActivationGroupDesc\f[R].
+The group descriptor specifies an optional
+\f[CB]ActivationGroupDesc.CommandEnvironment\f[R] that includes the
+command to execute to start the activation group and any command\-line
+options to be added to the command line.
+By default, the \f[CB]rmid\f[R] command uses the \f[CB]java\f[R] command
+found in \f[CB]java.home\f[R].
+The group descriptor also contains properties overrides that are added
+to the command line as options defined as:
+\f[CB]\-D\f[R]\f[I]property\f[R]\f[CB]=\f[R]\f[I]value\f[R].
+The \f[CB]com.sun.rmi.rmid.ExecPermission\f[R] permission grants the
+\f[CB]rmid\f[R] command permission to execute a command that\[aq]s
+specified in the group descriptor\[aq]s \f[CB]CommandEnvironment\f[R] to
+start an activation group.
+The \f[CB]com.sun.rmi.rmid.ExecOptionPermission\f[R] permission enables
+the \f[CB]rmid\f[R] command to use command\-line options, specified as
+properties overrides in the group descriptor or as options in the
+\f[CB]CommandEnvironment\f[R] when starting the activation group.
+When granting the \f[CB]rmid\f[R] command permission to execute various
+commands and options, the permissions \f[CB]ExecPermission\f[R] and
+\f[CB]ExecOptionPermission\f[R] must be granted to all code sources.
+.PP
+\f[CB]ExecPermission\f[R] class: Represents permission for the
+\f[CB]rmid\f[R] command to execute a specific command to start an
+activation group.
+.PP
+\f[CB]ExecPermission\f[R] syntax: The name of \f[CB]ExecPermission\f[R] is
+the path name of a command to grant the \f[CB]rmid\f[R] command permission
+to execute.
+.PP
+A path name that ends in a slash (\f[CB]/\f[R]) and an asterisk
+(\f[CB]*\f[R]) indicates that all of the files are contained in that
+directory where the slash is the file\-separator character,
+\f[CB]File.separatorChar\f[R].
+.PP
+A path name that ends in a slash (\f[CB]/\f[R]) and a minus sign
+(\f[CB]\-\f[R]) indicates that all files and subdirectories are contained
+in that directory (recursively).
+.PP
+A path name that consists of the special token \f[CB]<<ALL\ FILES>>\f[R]
+matches any file.
+.PP
+A path name that consists of an asterisk (\f[CB]*\f[R]) indicates that all
+the files are in the current directory.
+.PP
+A path name that consists of a minus sign (\f[CB]\-\f[R]) indicates that
+all the files are in the current directory and (recursively) all files
+and subdirectories are contained in the current directory.
+.PP
+\f[CB]ExecOptionPermission\f[R] class: Represents permission for the
+\f[CB]rmid\f[R] command to use a specific command\-line option when
+starting an activation group.
+The name of \f[CB]ExecOptionPermission\f[R] is the value of a
+command\-line option.
+.PP
+\f[CB]ExecOptionPermission\f[R] syntax: Options support a limited wild
+card scheme.
+An asterisk signifies a wild card match, and it can appear as the option
+name itself (matches any option), or an asterisk (*) can appear at the
+end of the option name only when the asterisk (\f[CB]*\f[R]) follows a dot
+(\f[CB]\&.\f[R]) or an equals sign (\f[CB]=\f[R]).
+.PP
+For example: \f[CB]*\f[R] or \f[CB]\-Dmydir.*\f[R] or \f[CB]\-Da.b.c=*\f[R] is
+valid, but \f[CB]*mydir\f[R] or \f[CB]\-Da*b\f[R] or \f[CB]ab*\f[R] isn\[aq]t
+valid.
+.PP
+\f[B]Policy file for rmid\f[R]
+.PP
+When you grant the \f[CB]rmid\f[R] command permission to execute various
+commands and options, the permissions \f[CB]ExecPermission\f[R] and
+\f[CB]ExecOptionPermission\f[R] must be granted to all code sources
+(universally).
+It is safe to grant these permissions universally because only the
+\f[CB]rmid\f[R] command checks these permissions.
+.PP
+An example policy file that grants various execute permissions to the
+\f[CB]rmid\f[R] command is:
+.IP \[bu] 2
+\f[B]Oracle Solaris:\f[R]
+.RS 2
+.IP
+.nf
+\f[CB]
+grant\ {
+\ \ \ \ permission\ com.sun.rmi.rmid.ExecPermission
+\ \ \ \ \ \ \ \ "/files/apps/java/jdk1.7.0/solaris/bin/java";
+
+\ \ \ \ permission\ com.sun.rmi.rmid.ExecPermission
+\ \ \ \ \ \ \ \ "/files/apps/rmidcmds/*";
+
+\ \ \ \ permission\ com.sun.rmi.rmid.ExecOptionPermission
+\ \ \ \ \ \ \ \ "\-Djava.security.policy=/files/policies/group.policy";
+
+\ \ \ \ permission\ com.sun.rmi.rmid.ExecOptionPermission
+\ \ \ \ \ \ \ \ "\-Djava.security.debug=*";
+
+\ \ \ \ permission\ com.sun.rmi.rmid.ExecOptionPermission
+\ \ \ \ \ \ \ \ "\-Dsun.rmi.*";
+};
+\f[R]
.fi
-.nf
-\f3 throws SecurityException;\fP
+.RE
+.IP \[bu] 2
+\f[B]Windows:\f[R]
+.RS 2
+.IP
+.nf
+\f[CB]
+grant\ {
+\ \ \ \ permission\ com.sun.rmi.rmid.ExecPermission
+\ \ \ \ \ \ \ \ "c:\\\\files\\\\apps\\\\java\\\\jdk1.7.0\\\\win\\\\bin\\\\java";
+
+\ \ \ \ permission\ com.sun.rmi.rmid.ExecPermission
+\ \ \ \ \ \ \ \ "c:\\\\files\\\\apps\\\\rmidcmds\\\\*";
+
+\ \ \ \ permission\ com.sun.rmi.rmid.ExecOptionPermission
+\ \ \ \ \ \ \ \ "\-Djava.security.policy=c:\\\\files\\\\policies\\\\group.policy";
+
+\ \ \ \ permission\ com.sun.rmi.rmid.ExecOptionPermission
+\ \ \ \ \ \ \ \ "\-Djava.security.debug=*";
+
+\ \ \ \ permission\ com.sun.rmi.rmid.ExecOptionPermission
+\ \ \ \ \ \ \ \ "\-Dsun.rmi.*";
+};
+\f[R]
.fi
-.nf
-\f3\fP
+.RE
+.PP
+The first permission granted allows the \f[CB]rmid\f[R] command to execute
+the 1.7.0 release of the \f[CB]java\f[R] command, specified by its
+explicit path name.
+By default, the version of the \f[CB]java\f[R] command found in
+\f[CB]java.home\f[R] is used (the same one that the \f[CB]rmid\f[R] command
+uses), and doesn\[aq]t need to be specified in the policy file.
+The second permission allows the \f[CB]rmid\f[R] command to execute any
+command in either the directory \f[CB]/files/apps/rmidcmds\f[R] (Oracle
+Solaris, Linux, and macOS) or the directory
+\f[CB]c:\\files\\apps\\rmidcmds\\\f[R] (Windows).
+.PP
+The third permission granted, \f[CB]ExecOptionPermission\f[R], allows the
+\f[CB]rmid\f[R] command to start an activation group that defines the
+security policy file to be either \f[CB]/files/policies/group.policy\f[R]
+(Oracle Solaris) or \f[CB]c:\\files\\policies\\group.policy\f[R]
+(Windows).
+The next permission allows the \f[CB]java.security.debug\ property\f[R] to
+be used by an activation group.
+The last permission allows any property in the
+\f[CB]sun.rmi\ property\f[R] name hierarchy to be used by activation
+groups.
+.PP
+To start the \f[CB]rmid\f[R] command with a policy file, the
+\f[CB]java.security.policy\f[R] property needs to be specified on the
+\f[CB]rmid\f[R] command line, for example:
+.PP
+\f[CB]rmid\ \-J\-Djava.security.policy=rmid.policy\f[R].
+.RE
+.IP \[bu] 2
+\f[I]policyClassName\f[R]
+.RS 2
+.PP
+If the default behavior isn\[aq]t flexible enough, then an administrator
+can provide, when starting the \f[CB]rmid\f[R] command, the name of a
+class whose \f[CB]checkExecCommand\f[R] method is executed to check
+commands to be executed by the \f[CB]rmid\f[R] command.
+.PP
+The \f[CB]policyClassName\f[R] specifies a public class with a public,
+no\-argument constructor and an implementation of the following
+\f[CB]checkExecCommand\f[R] method:
+.IP
+.nf
+\f[CB]
+\ public\ void\ checkExecCommand(ActivationGroupDesc\ desc,\ String[]\ command)
+\ \ \ \ \ \ \ \ throws\ SecurityException;
+\f[R]
.fi
-.sp
-
-
-Before starting an activation group, the \f3rmid\fR command calls the policy\&'s \f3checkExecCommand\fR method and passes to it the activation group descriptor and an array that contains the complete command to start the activation group\&. If the \f3checkExecCommand\fR throws a \f3SecurityException\fR, then the \f3rmid\fR command does not start the activation group and an \f3ActivationException\fR is thrown to the caller attempting to activate the object\&.
-.TP 0.2i
-\(bu
-none
-
-If the \f3sun\&.rmi\&.activation\&.execPolicy\fR property value is \f3none\fR, then the \f3rmid\fR command does not perform any validation of commands to start activation groups\&.
+.PP
+Before starting an activation group, the \f[CB]rmid\f[R] command calls the
+policy\[aq]s \f[CB]checkExecCommand\f[R] method and passes to it the
+activation group descriptor and an array that contains the complete
+command to start the activation group.
+If the \f[CB]checkExecCommand\f[R] throws a \f[CB]SecurityException\f[R],
+then the \f[CB]rmid\f[R] command doesn\[aq]t start the activation group
+and an \f[CB]ActivationException\f[R] is thrown to the caller attempting
+to activate the object.
+.RE
+.IP \[bu] 2
+\f[CB]none\f[R]
+.RS 2
+.PP
+If the \f[CB]sun.rmi.activation.execPolicy\f[R] property value is
+\f[CB]none\f[R], then the \f[CB]rmid\f[R] command doesn\[aq]t perform any
+validation of commands to start activation groups.
+.RE
.RE
-
.TP
--log \fIdir\fR
-.br
-Specifies the name of the directory the activation system daemon uses to write its database and associated information\&. The log directory defaults to creating a log, in the directory in which the \f3rmid\fR command was executed\&.
+.B \f[CB]\-log\f[R] \f[I]dir\f[R]
+Specifies the name of the directory that the activation system daemon
+uses to write its database and associated information.
+The log directory defaults to creating a log, in the directory in which
+the \f[CB]rmid\f[R] command was executed.
+.RS
+.RE
.TP
--port \fIport\fR
-.br
-Specifies the port the registry uses\&. The activation system daemon binds the \f3ActivationSystem\fR, with the name \f3java\&.rmi\&.activation\&.ActivationSystem\fR, in this registry\&. The \f3ActivationSystem\fR on the local machine can be obtained using the following \f3Naming\&.lookup\fR method call:
-.sp
-.nf
-\f3import java\&.rmi\&.*; \fP
-.fi
-.nf
-\f3 import java\&.rmi\&.activation\&.*;\fP
-.fi
-.nf
-\f3\fP
-.fi
-.nf
-\f3 ActivationSystem system; system = (ActivationSystem)\fP
-.fi
-.nf
-\f3 Naming\&.lookup("//:port/java\&.rmi\&.activation\&.ActivationSystem");\fP
-.fi
+.B \f[CB]\-port\f[R] \f[I]port\f[R]
+Specifies the port that the registry uses.
+The activation system daemon binds \f[CB]ActivationSystem\f[R], with the
+name \f[CB]java.rmi.activation.ActivationSystem\f[R], in this registry.
+The \f[CB]ActivationSystem\f[R] on the local machine can be obtained using
+the following \f[CB]Naming.lookup\f[R] method call:
+.RS
+.IP
.nf
-\f3\fP
+\f[CB]
+import\ java.rmi.*;
+import\ java.rmi.activation.*;
+
+ActivationSystem\ system;\ system\ =\ (ActivationSystem)
+Naming.lookup("//:port/java.rmi.activation.ActivationSystem");
+\f[R]
.fi
-.sp
-
-.TP
--stop
-.br
-Stops the current invocation of the \f3rmid\fR command for a port specified by the \f3-port\fR option\&. If no port is specified, then this option stops the \f3rmid\fR invocation running on port 1098\&.
-.SH ENVIRONMENT\ VARIABLES
+.RE
.TP
-CLASSPATH
-Used to provide the system a path to user-defined classes\&. Directories are separated by colons, for example: \f3\&.:/usr/local/java/classes\fR\&.
-.SH SEE\ ALSO
-.TP 0.2i
-\(bu
-java(1)
-.TP 0.2i
-\(bu
-Setting the Class Path
-.RE
-.br
-'pl 8.5i
-'bp
+.B \f[CB]\-stop\f[R]
+Stops the current invocation of the \f[CB]rmid\f[R] command for a port
+specified by the \f[CB]\-port\f[R] option.
+If no port is specified, then this option stops the \f[CB]rmid\f[R]
+invocation running on port 1098.
+.RS
+.RE
< prev index next >