39e085accf228684b9573bc8ad707a364ed6242e 1701 |
|
25-Apr-2007 |
jvergara |
Fix for issue 1273 (exception if JAVA_HOME undefined in scripts).
The fix consists of modifying the scripts to launch the InstallDS classwith a test option using the JVM
that was found. If the JVM can be successfully launched, the JVM is compatible with 1.5, if not we as
sume that is not compatible with JDK 1.5.
The downside of the fix is that it requires an additional start of the JVM each time the command line i
s launched. That is why the fix only applies to setup, uninstall, upgrade, start and stop command lines. The modifications in _server-script.* and _client-script.sh just modify the message displayed when a JVM could not be found (informing that JDK 1.5 or later can be used). |
266c5071a91fda6a5159b08ea8d45261228d03d5 702 |
|
11-Nov-2006 |
neil_a_wilson |
Make a number of changes to administrative tools provided with OpenDS. These
are all made under the umbrella of issue #994, but there are individual issues
for each change.
- Issue #979 -- Re-order LDAP tool arguments
When displaying usage information for many of the LDAP tools (e.g.,
ldapsearch, ldapmodify, etc.), the arguments were not provided in any kind of
logical grouping. This has been corrected so that the arguments are listed
in a more logical ordering.
- Issue #983 -- Add tool description to argument parser
When displaying usage information for administrative tools, it now includes a
small summary of what the tool does at the top of the argument list.
- Issue #984 -- Make tool usage more compact
Previously, the tool usage included a blank line between each argument, which
made the usage information seem too verbose, especially for tools like
ldapsearch with a lot of arguments. This extra space has been removed.
Also, many of the argument descriptions have been rewritten in an attempt to
avoid requiring multiple lines.
- Issue #985 -- Wrap long output in administrative tools when appropriate
Update most of the output for the administrative tools so that it is easier
to read on 80-column displays. This primarily impacts error message, and
cases in which the format of the output is important (e.g., LDIF output from
ldapsearch) no changes were made.
- Issue #986 -- Eliminate hard-coded strings in tools
Some of the tools had hard-coded strings used for error and warning messages.
They have been replaced with localizeable output from the messages files.
- Issue #990 -- LDAP tools don't use trust store password
The LDAP tools didn't provide any mechanism for specifying the PIN needed to
access the contents of an SSL trust store. Some types of trust stores may
require a PIN to access them, so it is now possible to either directly
specify the PIN or to provide the path to a PIN file.
- Issue #991 -- Disconnect when running stop-ds shouldn't be an error
When using the stop-ds script, if the server began shutting down before it
returned a response to the client, the client would provide an error message
making it sound like something went wrong. The output has now been updated
to indicate that the server is likely in the course of shutting down.
- Issue #992 -- Tool usage should include the tool name rather than the class
When displaying usage information for the administrative tools, the
fully-qualified class name for the Java class was displayed, where the name
of the shell script or batch file would have been more useful. |
0cf0e19d7abb0e7659df6d191269f96b3ffe7f45 640 |
|
25-Oct-2006 |
neil_a_wilson |
Make several changes to administrative shell scripts provided with OpenDS.
All of these changes fall under the blanket of issue 882, but are also
associated with a number of individual sub-issues.
The changes include:
- Create new "_client-script.sh" and "_server-script.sh" shell scripts that
hold the majority of the logic required to launch the client-side and
server-side tools (Issue #873).
- Explicitly set the PATH, LD_LIBRARY_PATH, and LD_PRELOAD (and the 32-bit and
64-bit specific variants of LD_LIBRARY_PATH and LD_PRELOAD) to ensure better
security and more consistent behavior when invoking external commands
(Issue #607).
- Fix potential problems that could arise if either OpenDS or the Java runtime
are installed in a path that contains spaces (Issue #820).
- Update the start-ds.sh script so that it always creates a PID file, whether
running in the foreground or in the background (Issue #859).
- Update the start-ds.sh script so that when running in the background it will
not exit until it confirms that the server is actually running. It will also
display any messages written to standard output/standard error during
startup (Issue #590).
- Update the stop-ds.sh script so that it can either perform a local stop (via
kill with the TERM signal) or a remote stop (over LDAP using the shutdown
task). If the script is invoked with no arguments and there is a local PID
file present, then it will be a local stop via kill, and it will wait until
the server actually has stopped before exiting. Otherwise it will be a
remote stop over LDAP (Issue #871). |