Changes in stop-ds http://src.iws.cs.ovgu.de/source/rss/forgerock/opendj2/resource/bin/stop-ds en Copyright 2005 Java 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/stop-ds - 0f8553e2af5fc49a510ecfcfc93e66d06713f631 ludo Fix OpenDJ-222: Remove more references to OpenDS. Also update/adds the man-pages for tools. /forgerock/opendj2/resource/bin/stop-ds - 814920a099ee946453263e682c7bb2cda00b7983 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/stop-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/stop-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/stop-ds - e3936cbb8c38994e9de122ab9dbe7b6e55f1c834 jvergara Fix for issue #3626 (Occurrences of grep, cat,... commands should be replaced with sh built-in commands) Replace occurrences of 'cat' and 'grep' by shell builtin command. /forgerock/opendj2/resource/bin/stop-ds - 773465ac0ffcb0c5856718e21f59cdc671a99c4a lutoff Frontport of all fixes related to SVR4 from branch 1.2 to trunk: 3646 configure script fails to retrieve the user/group of the ins 3647 Missing license file 3648 Third party license files should be merged 3649 Wrong copyright file in SVR4 package 3650 LDAP tools are missing in SVR4 package 3651 Server is not stopped after package removal 3654 SVR4 pkginfo not compliant with Solaris rules 3658 no man pages in SVR4 package 3661 SVR4 only: OpenDS fails to start with 1.1.0 bld3 3663 SVR4: unable to start OpenDS if user has no home directory 3664 SVR4: delimiter used in copyright file is not the one define 3706 configure: configure -H/-V doesn't work when the instance is 3707 unconfigure: unconfigure --wrongoption should display the us 3708 stop-ds: stop-ds -R doesn't work 3729 incorrect exit codes for configure/unconfigure scripts 3735 OpenDS failed to start if build number contains version qual /forgerock/opendj2/resource/bin/stop-ds - 6733dfd94dda39b3bce6e9fe9713d4d2379cbb85 chebrard 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/stop-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/stop-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/stop-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/stop-ds - 014019918f7e3844f558f6159b8d41517254edc2 lutoff 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/stop-ds - 3cedecd5ea21cca5d9709abf320a2082cd3694e5 jvergara Updated the copyright statement to reflect that Sun owns the full copyright on the project files. /forgerock/opendj2/resource/bin/stop-ds - a3d3ab94806056d2355afea6fe8daac41059b9fb ludovicp Fix for issue 2902 (stop-ds -R restarts the server with client tool JVM) When the java properties are set to not overwrite the environment variables (which is the default behavior) when we call start-ds from the stop-ds scripts, OPENDS_JAVA_ARGS is already set with the arguments for the stop (client arguments). The fix consists basically on resetting the environment variables to those we had before calling stop-ds before calling start-ds. /forgerock/opendj2/resource/bin/stop-ds - 7b94de75a19ac6d37a440a7915ae0c7b7c024527 jvergara 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/stop-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/stop-ds - 37f9a536593b696e5a3dcec443e1475f22fb5afd 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/stop-ds - 61ae414d98d24ba4a72a905b07db9424353669f4 neil_a_wilson Add a mechanism for generating an RC script that can be used on UNIX systems to configure the server to automatically start when the system boots. Also, update the stop-ds script so that if the server is to be stopped via kill but no PID file is present, the stop script will generate an error instead of trying to invoke the stop task (which is guaranteed to fail since the attempt will be made anonymously, and this will give a confusing error message). OpenDS Issue Number: 526 /forgerock/opendj2/resource/bin/stop-ds - 86580987a3bc88a2018319660f3b536c381938f5 neil_a_wilson Complete fix for 1252 restrict installed bin files to relevant platform. The bat files are only under 'bat' directory and some function scripts that are not targetted to be used by the user (_server-script, _client-script, etc.) have been moved now to lib. /forgerock/opendj2/resource/bin/stop-ds - 9da44d3de0a7180285a77b7e8d2426a72aca249e 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). /forgerock/opendj2/resource/bin/stop-ds - 39e085accf228684b9573bc8ad707a364ed6242e jvergara