start-ds revision 830
295N/A# The contents of this file are subject to the terms of the 295N/A# Common Development and Distribution License, Version 1.0 only 295N/A# (the "License"). You may not use this file except in compliance 295N/A# You can obtain a copy of the license at 295N/A# See the License for the specific language governing permissions 295N/A# and limitations under the License. 295N/A# When distributing Covered Code, include this CDDL HEADER in each 295N/A# file and include the License file at 295N/A# add the following below this CDDL HEADER, with the fields enclosed 295N/A# by brackets "[]" replaced with your own identifying * information: 295N/A# Portions Copyright [yyyy] [name of copyright owner] 295N/A# Portions Copyright 2006-2007 Sun Microsystems, Inc. 295N/A# Capture the current working directory so that we can change to it later. 295N/A# Then capture the location of this script and the Directory Server instance 295N/A# root so that we can use them to create appropriate paths. 295N/A# See if JAVA_HOME is set. If not, then see if there is a java executable in 295N/A# the path and try to figure it out. 295N/Aif test -z
"${JAVA_BIN}" 295N/A if test -z
"${JAVA_HOME}" echo "Please set JAVA_HOME to the root of a Java 5.0 installation." # Explicitly set the PATH, LD_LIBRARY_PATH, LD_PRELOAD, and other important # system environment variables for security and compatibility reasons. # Configure the appropriate CLASSPATH. # Specify the locations of important files that may be used when the server # Specify the script name so that it may be provided in command-line usage. # See if the provided set of arguments were sufficient for us to be able to # start the server or perform the requested operation. An exit code of 99 # means that it should be possible to start the server. An exit code of 98 # means that the server is already running and we shouldn't try to start it. # An exit code of anything else means that we're not trying to start the server # and we can just exit with that exit code. # See if an "-N" or a "--nodetach" argument was provided as a command-line # argument. If it was, then don't use nohup to send to the background, and # send all output to both the console and a lot file. if test "${ARG}" =
"--nodetach" rm -f
"${PID_FILE}" "${LOG_FILE}" --
configFile "${CONFIG_FILE}" "${@}" >
"${LOG_FILE}" 2>&
1 &