Changes in start-ds http://src.iws.cs.ovgu.de/source/rss/forgerock/opendj2/resource/bin/start-ds en Copyright 2005 Java svn merge https://svn.forgerock.org/opendj/trunk/opends@8851 https://svn.forgerock.org/opendj/branches/native-packaging@8851 . /forgerock/opendj2/resource/bin/start-ds - a5b9f8fb834b1b2208e59a2fa76714bd91a5f147 violette Fix issue OPENDJ-732: Both start-ds and set-java-home were missing quotes around variables, and failed if the Java path contains spaces (like with QuickSetup on Mac OSX, which uses the Plugin JRE). /forgerock/opendj2/resource/bin/start-ds - 6e041baef82b526dc9a1548dae116ab37da34dcb ludo Fix for OPENDJ-222 : Renamed environment variables to OPENDJ_... Updated scripts so that if OPENDJ_JAVA_HOME and OPENDJ_JAVA_ARGS are not defined, we look at the legacy OPENDS_... ones. /forgerock/opendj2/resource/bin/start-ds - 0f8553e2af5fc49a510ecfcfc93e66d06713f631 ludo Add support for SVR4 packages for OpenDJ. Package name is opendj. It's a single package and has integration with SMF. Default installation is /usr/opendj. Once packages are installed, root must run configure to setup the Instance location (/var/opendj) and owner. And the owner must run setup. /forgerock/opendj2/resource/bin/start-ds - d3ce44d37110c284dad15122841fd97ee41d9ac5 ludo Follow up to the fix for issue 4081 (start-ds and stop-ds fails on Mac OS X with latest JVM). Use the '-client' option to launch small programs inside the scripts. /forgerock/opendj2/resource/bin/start-ds - 7a76def451cc02fcd02d8d6ff35d4751db91b206 jvergara Fix for issue 4081 (start-ds and stop-ds fails on Mac OS X with latest JVM) The scripts used to impose a maximum and minimum size for the JVM to reduce the time required to launch the JVM when using some small and auxiliary Java programs. This generates ugly errors in some platforms, so the fix consists on playing safe and rely on the JVM ergonomics to launch these programs. /forgerock/opendj2/resource/bin/start-ds - e3936cbb8c38994e9de122ab9dbe7b6e55f1c834 jvergara Fix for issue #3814 : start-ds script return before server has started /forgerock/opendj2/resource/bin/start-ds - 186f94aaee0ba7f253e09c491a3a513cbabea65f jcambon Change test == to test = for strings, as == is a ksh form and doesn't work on Solaris 10 /bin/sh. (In openSolaris /bin/sh = ksh93). /forgerock/opendj2/resource/bin/start-ds - 2ed4722b4c052dcfe7884519a119e68a295f77af ludovicp Provide suppport for SMF for the SVR4 packages. A SMF manifest is delivered in /usr/opends/resources/opends-manifest.xml The manifest is edited and copied under /var/svc/manifest/network/ldap by the configure command (will be committed later), and imported via svccfg. start-ds / stop-ds / control-panel can be used to start /stop the server. They temporarily enable/disable the opends service. Use svcadm enable opends to permanently enable OpenDS to start at boot time. /forgerock/opendj2/resource/bin/start-ds - 44a7ec1a853804826c90cda2fbb4ac712c86bbaa ludovicp Fix 3534: Provide native Solaris packages (fix also 3533: upgrade fails starting server adding entry ds-cfg-key-id) /forgerock/opendj2/resource/bin/start-ds - d319724fed3be916a9f68676aac6eb203d44b551 chebrard These changes are separating the current delivery into an "Install Layout" (the binaries) and an "Instance Layout" (the user data). /forgerock/opendj2/resource/bin/start-ds - 014019918f7e3844f558f6159b8d41517254edc2 lutoff Fix for issue 3237 (On Windows, start-ds -Q doesn't start the server) There are a couple of issues here: 1. The start-ds.bat file must be updated to handle correctly the -Q option. 2. The start-ds shell file must be updated to handle correctly the nodetach and quiet options together. /forgerock/opendj2/resource/bin/start-ds - 61491a8f67f7eae3967ce28737730583c6ad922d jvergara Second part of fix for issue 3126 (Cannot run setup if unziped in directory with spaces in name). These changes allow to execute the scripts from different directories than the one the script is located at. /forgerock/opendj2/resource/bin/start-ds - 3cedecd5ea21cca5d9709abf320a2082cd3694e5 jvergara Updated the copyright statement to reflect that Sun owns the full copyright on the project files. /forgerock/opendj2/resource/bin/start-ds - a3d3ab94806056d2355afea6fe8daac41059b9fb ludovicp 2730: New - The setup command should perform some basic memory tuning Note: this issue is not fully covered by the proposed modifications but all that is missing in order to fix it is to figure out which are the default memory values that we want to propose in the setup. 2620: Server should be started as server JRE and clients should be started as client JREs The proposed solution goes beyond fixing the two issues and proposes a manner for the user to set specific java arguments (and use a specific JVM) for every command-line. Today the user can specify the JVM to be used using the OPENDS_JAVA_HOME environment variable and the java arguments by using the OPENDS_JAVA_ARGS environment variable. In the case of the JVM this covers most of the use cases (in general we will use the same JVM for all the command-lines). However this is quite limiting in the case of the java arguments we pass. For instance in general we want to run the server (start-ds command-line) using the server mode of the JVM but other command-lines using the -client mode of the JVM. In the same manner we might want to have a bigger heap when running the server than when we are running a "lightweight" utility as dsconfig. The proposed solution is to have a properties file called java.properties where the user specifies the different JVM and java arguments to be used for every command-line. Once the user has edited this properties file, (s)he must run a command-line called dsjavaproperties that will update all the scripts to use the arguments specified in that properties file. NOTE: there are a number of command-lines (import-ldif, export-ldif, backup, restore) where the user will be able to specify different java arguments (and different JVM) to use depending on whether the command-line is run in online or offline modes. You can see the comments on java.properties to get more information about this and in general about the different properties that can be set. The modification in the setup basically try to check if the JVM that is being used to run the setup (the one that will be used by default) supports the -client and -server options. Depending on the results of these checks the setup will update the java.properties file and then run dsjavaproperties to update the scripts. /forgerock/opendj2/resource/bin/start-ds - 27f8adec83293fb8bd3bfa37175322b0ee3bb933 jvergara Fix for issue 2035 (Use OpenDS specific environment variables to determine the JVM to be used.) Use two environment variables to know which is the JVM to be used by the scripts: OPENDS_JAVA_BIN and OPENDS_JAVA_HOME. When the setup creates the file lib/set-java-home it writes the contents of OPENDS_JAVA_HOME to it (instead of JAVA_HOME which was the previous behavior). Before these changes, the scripts used to look for JAVA_BIN, then JAVA_HOME and finally for the contents of the set-java-home file. The problem with this approach is that if the user required to specify JAVA_HOME or JAVA_BIN to an unsupported version of the JDK (because some other program in the machine had this requirement) the scripts of OpenDS could not run. Now the checks that we do to figure out the JVM are done in the following order: 1. Check if OPENDS_JAVA_BIN is defined in the environment. 2. Check if OPENDS_JAVA_HOME is defined in the environment. 3. Check if OPENDS_JAVA_HOME is defined in the lib/set-java-home file. 4. Check if JAVA_BIN is defined in the environment. 5. Check if JAVA_HOME is defined in the environment. 6. Check if we can figure out the java installation by executing "type java" (in UNIX environments). If any of the above checks is positive, we will try to use the JVM found. Extras: the uninstall script on UNIX now checks that we are using a JDK compatible with 1.5 and displays a user friendly message if it does not. /forgerock/opendj2/resource/bin/start-ds - 37f9a536593b696e5a3dcec443e1475f22fb5afd jvergara Update the start-ds script to eliminate a warning message about the inability to acquire a lock file. The server was functioning properly, but the message should not have been printed. OpenDS Issue Number: 2242 /forgerock/opendj2/resource/bin/start-ds - ca7fd1a989fecd15241ed293d67750c6049d06d2 neil_a_wilson Fix for issue 2187 (start-ds dos not return proper error code). Use the --checkstartability option to know if the server is running or not and return the proper error code accordingly. /forgerock/opendj2/resource/bin/start-ds - fbae67e0ce2395d66b4cec5b17c54ddf8dd3dcb2 jvergara Update the CreateRCScript tool so that it provides the ability to specify the user that the server should run as (invoked via "su"), and also lets the user specify the JAVA_HOME and JAVA_ARGS settings that should be used. This also updates the start-ds and stop-ds commands to support a --quiet argument, which causes them to not generate any output. The generated RC script uses this option, since server startup output shouldn't be generated at system boot time. /forgerock/opendj2/resource/bin/start-ds - 61ae414d98d24ba4a72a905b07db9424353669f4 neil_a_wilson Update the start-ds script so that it uses "Java.5.0 or higher" instead of just "Java 5.0". Also, if JAVA_ARGS is given and there's a chance the arguments are invalid, then include a message indicating that the user should check them. OpenDS Issue Number: 1801 /forgerock/opendj2/resource/bin/start-ds - dc37d95e0fd16537e3109317a95398172930a7b0 neil_a_wilson