--- a/jdk/src/solaris/doc/sun/man/man1/rmid.1 Thu Apr 30 15:04:39 2009 -0700
+++ b/jdk/src/solaris/doc/sun/man/man1/rmid.1 Mon May 04 18:28:26 2009 -0700
@@ -1,5 +1,4 @@
-.'" t
-." Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
+." Copyright 2004-2006 Sun Microsystems, Inc. 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
@@ -19,20 +18,21 @@
." Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,
." CA 95054 USA or visit www.sun.com if you need additional information or
." have any questions.
-." `
-.TH rmid 1 "05 Aug 2006"
-." Generated by html2roff
-.\\" Changed by: Ann Wollrath \- JavaSoft East, 2\-Mar\-2000
-.\\" Changed by: Jen McGinn \- Jini Technology Software, 6\-Mar\-2000
+."
+.TH rmid 1 "04 May 2009"
+." Generated from HTML by html2man (author: Eric Armstrong)
+
.LP
-.SH NAME
+.SH "Name"
rmid \- The Java RMI Activation System Daemon
.LP
+.RS 3
.LP
.LP
\f3rmid\fP starts the activation system daemon that allows objects to be registered and activated in a virtual machine (VM).
.LP
+.RE
.SH "SYNOPSIS"
.LP
@@ -55,7 +55,7 @@
.na
\f2Java RMI Specification\fP @
.fi
-http://java.sun.com/javase/6/docs/platform/rmi/spec/rmitoc.html and
+http://java.sun.com/javase/6/docs/platform/rmi/spec/rmiTOC.html and
.na
\f2Activation tutorials\fP @
.fi
@@ -81,10 +81,10 @@
.LP
.RS 3
.TP 2
-*
+o
starts the Activator and an internal registry on the default port, 1098, and
.TP 2
-*
+o
binds an \f2ActivationSystem\fP to the name \f2java.rmi.activation.ActivationSystem\fP in this internal registry.
.RE
@@ -105,8 +105,7 @@
starts the activation system daemon and a registry on the registry's default port, 1099.
.LP
.SS
-Starting rmid from
-inetd/xinetd
+Starting rmid from inetd/xinetd
.LP
.LP
An alternative to starting \f2rmid\fP from the command line is to configure \f2inetd\fP (Solaris) or \f2xinetd\fP (Linux) to start \f2rmid\fP on demand.
@@ -119,13 +118,13 @@
.LP
.RS 3
.TP 2
-*
+o
Output printed to \f2System.err\fP is redirected to a file. This file is located in the directory specified by the \f2java.io.tmpdir\fP system property (typically \f2/var/tmp\fP or \f2/tmp\fP) with the prefix \f2"rmid\-err"\fP and the suffix \f2"tmp"\fP.
.TP 2
-*
+o
The \f2\-port\fP option is disallowed. If this option is specified, \f2rmid\fP will exit with an error message.
.TP 2
-*
+o
The \f2\-log\fP option is required. If this option is not specified, \f2rmid\fP will exit with an error message.
.RE
@@ -137,6 +136,7 @@
.LP
.LP
+.RS 3
.TP 3
\-C<someCommandLineOption>
Specifies an option that is passed as a command\-line argument to each child process (activation group) of \f2rmid\fP when that process is created. For example, you could pass a property to each virtual machine spawned by the activation system daemon:
@@ -168,13 +168,12 @@
\fP
.fi
.TP 3
-
\-J\-Dsun.rmi.activation.execPolicy=<policy>
Specifies the policy that \f2rmid\fP employs to check commands and command\-line options used to launch the VM in which an activation group runs. Please note that this option exists only in Sun's implementation of the Java RMI activation daemon. If this property is not specified on the command line, the result is the same as if \f2\-J\-Dsun.rmi.activation.execPolicy=default\fP were specified. The possible values of \f2<policy>\fP can be \f2default\fP, \f2<policyClassName>\fP, or \f2none\fP:
.LP
.RS 3
.TP 2
-*
+o
\f3default (or if this property is \fP\f4unspecified\fP\f3)\fP
.LP
The default \f2execPolicy\fP allows \f2rmid\fP to execute commands with specific command\-line options only if \f2rmid\fP has been granted permission to execute those commands and options in the security policy file that \f2rmid\fP uses. Only the default activation group implementation can be used with the \f2default\fP execution policy.
@@ -190,7 +189,8 @@
.LP
The permission \f2com.sun.rmi.rmid.ExecPermission\fP is used to grant \f2rmid\fP permission to execute a command, specified in the group descriptor's \f2CommandEnvironment\fP to launch an activation group. The permission \f2com.sun.rmi.rmid.ExecOptionPermission\fP is used to allow \f2rmid\fP to use command\-line options, specified as properties overrides in the group descriptor or as options in the \f2CommandEnvironment\fP, when launching the activation group.
.LP
-When granting \f2rmid\fP permission to execute various commands and options, the permissions \f2ExecPermission\fP and \f2ExecOptionPermission\fP need to be granted universally (i.e., granted to all code sources).
+When granting \f2rmid\fP permission to execute various commands and options, the permissions \f2ExecPermission\fP and \f2ExecOptionPermission\fP need to be granted universally (i.e., granted to all code sources).
+.RS 3
.TP 3
ExecPermission
The \f2ExecPermission\fP class represents permission for \f2rmid\fP to execute a specific \f2command\fP to launch an activation group.
@@ -210,8 +210,7 @@
.LP
For example: "*" or "\-Dfoo.*" or "\-Da.b.c=*" is valid, "*foo" or "\-Da*b" or "ab*" is not.
.TP 3
-Policy file for
-rmid
+Policy file for rmid
When granting \f2rmid\fP permission to execute various commands and options, the permissions \f2ExecPermission\fP and \f2ExecOptionPermission\fP need to be granted universally (i.e., granted to all code sources). It is safe to grant these permissions universally because only \f2rmid\fP checks these permissions.
.LP
An example policy file that grants various execute permissions to \f2rmid\fP is:
@@ -222,13 +221,7 @@
.fl
permission com.sun.rmi.rmid.ExecPermission
.fl
- "/files/apps/java/jdk1.2.2/solaris/bin/java";
-.fl
-
-.fl
- permission com.sun.rmi.rmid.ExecPermission
-.fl
- "/files/apps/java/jdk1.2.2/solaris/bin/java_g";
+ "/files/apps/java/jdk1.7.0/solaris/bin/java";
.fl
.fl
@@ -258,9 +251,9 @@
.fl
\fP
.fi
-The first two permissions granted allow \f2rmid\fP to execute the 1.2.2 version of the \f2java\fP and \f2java_g\fP commands, specified by their explicit path names. Note that by default, the version of the \f2java\fP command found in \f2java.home\fP is used (the same one that \f2rmid\fP uses), and does not need to be specified in the policy file. The third permission allows \f2rmid\fP to execute any command in the directory \f2/files/apps/rmidcmds\fP.
+The first permission granted allow \f2rmid\fP to execute the 1.7.0 version of the \f2java\fP command, specified by its explicit path name. Note that by default, the version of the \f2java\fP command found in \f2java.home\fP is used (the same one that \f2rmid\fP uses), and does not need to be specified in the policy file. The second permission allows \f2rmid\fP to execute any command in the directory \f2/files/apps/rmidcmds\fP.
.LP
-The fourth permission granted, an \f2ExecOptionPermission\fP, allows \f2rmid\fP to launch an activation group that defines the security policy file to be \f2/files/policies/group.policy\fP. The next permission allows the \f2java.security.debug\fP property to be used by an activation group. The last permission allows any property in the \f2sun.rmi\fP property name hierarchy to be used by activation groups.
+The third permission granted, an \f2ExecOptionPermission\fP, allows \f2rmid\fP to launch an activation group that defines the security policy file to be \f2/files/policies/group.policy\fP. The next permission allows the \f2java.security.debug\fP property to be used by an activation group. The last permission allows any property in the \f2sun.rmi\fP property name hierarchy to be used by activation groups.
.LP
To start \f2rmid\fP with a policy file, the \f2java.security.policy\fP property needs to be specified on \f2rmid\fP's command line, for example:
.RS 3
@@ -270,10 +263,12 @@
\f2rmid \-J\-Djava.security.policy=rmid.policy\fP
.LP
.RE
+.RE
.TP 2
-*
+o
+.LP
.TP 2
-*
+o
\f4<policyClassName>\fP
.LP
If the default behavior is not flexible enough, an administrator can provide, when starting \f2rmid\fP, the name of a class whose \f2checkExecCommand\fP method is executed in order to check commands to be executed by rmid.
@@ -293,14 +288,16 @@
Before launching an activation group, \f2rmid\fP calls the policy's \f2checkExecCommand\fP method, passing it the activation group descriptor and an array containing the complete command to launch the activation group. If the \f2checkExecCommand\fP throws a \f2SecurityException\fP, \f2rmid\fP will not launch the activation group and an \f2ActivationException\fP will be thrown to the caller attempting to activate the object.
.LP
.TP 2
-*
+o
\f3none\fP
.LP
If the \f2sun.rmi.activation.execPolicy\fP property value is "none", then \f2rmid\fP will not perform any validation of commands to launch activation groups.
.RE
+.LP
.TP 3
\-log dir
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 directory, \f2log\fP, in the directory in which the \f2rmid\fP command was executed.
+.LP
.TP 3
\-port port
Specifies the port \f2rmid\fP's registry uses. The activation system daemon binds the \f2ActivationSystem\fP, with the name \f2java.rmi.activation.ActivationSystem\fP, in this registry. Thus, the \f2ActivationSystem\fP on the local machine can be obtained using the following \f2Naming.lookup\fP method call:
@@ -320,11 +317,13 @@
.fi
.TP 3
\-stop
-Stops the current invocation of \f2rmid\fP, for a port specified by the \f2\-port\fP option. If no port is specified, it will stop the \f2rmid\fP running on port 1098.
+Stops the current invocation of \f2rmid\fP, for a port specified by the \f2\-port\fP option. If no port is specified, it will stop the \f2rmid\fP running on port 1098.
+.RE
.SH "ENVIRONMENT VARIABLES"
.LP
.LP
+.RS 3
.TP 3
CLASSPATH
Used to provide the system a path to user\-defined classes. Directories are separated by colons. For example:
@@ -335,6 +334,7 @@
.fl
\fP
.fi
+.RE
.LP
.SH "SEE ALSO"
@@ -342,7 +342,11 @@
.LP
.LP
-rmic, CLASSPATH, java
+rmic(1),
+.na
+\f2CLASSPATH\fP @
+.fi
+http://java.sun.com/javase/6/docs/technotes/tools/index.html#classpath, java(1)
.LP
.LP