PUBLIC COMMENTS
This RFE is being filed because RFE 4295885 (considered important for Tiger) depends on this feature.
RFE 4295885 (RMI applications should be startable from inted) describes
the issue that RMI applications can't be launched via inetd. There is a
more general problem that a Java networking application (which includes
RMI applications) can't be launched via inetd. A solution to the general
problem needs to be addressed first before 4295885 can be addressed.
Background [mostly from 4295885]:
An increasing number of Solaris daemons [WBEM/Common System Management Web
Console] are being written using Java-based networking applications that use
either Java sockets or socket-based technology such as RMI. Normally daemons
like this would be started using inetd which starts processes in response to
requests over specific ports.
Currently, Java networking applications can't be launched via inetd, since
there's no way to convert a file descriptor inherited by the process from inetd
into a server socket that can be used by the application. As a result,
daemons using Java networking must be started at system boot time, whether or
not they will be needed. This hurts boot performance and wastes memory and
swap space, since often these services aren't used at all. Also
customers can't configure (i.e., disable) these services in the normal
way they're used to configuring networking services (editing
/etc/inet/inetd.conf).
|
Java