p4p_base #2

  • //
  • guest/
  • alan_petersen/
  • sdp/
  • dev/
  • Server/
  • Unix/
  • p4/
  • common/
  • bin/
  • p4p_base
  • View
  • Commits
  • Open Download .zip Download (3 KB)
#!/bin/bash
#------------------------------------------------------------------------------
# Copyright (c) Perforce Software, Inc., 2007-2015. All rights reserved
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are met:
#
# 1  Redistributions of source code must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
# 2.  Redistributions in binary form must reproduce the above copyright
#     notice, this list of conditions and the following disclaimer in the
#     documentation and/or other materials provided with the distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL PERFORCE
# SOFTWARE, INC. BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
# ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
# TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
# THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
# DAMAGE.
#------------------------------------------------------------------------------

#
# Perforce proxy base init script

# do nothing unless $SDP_INSTANCE is defined.
if [[ -z $SDP_INSTANCE ]]; then
   echo $SDP_INSTANCE
   echo "SDP_INSTANCE is invalid."
   exit 1
fi

if [[ `$ID -u` = 0 ]]; then
   exec su - $OSUSER -c "$0 $1"
elif [ "`$ID -u -n`" != $OSUSER ]; then
   echo "$0 can only be run by root or $OSUSER"
   exit 1
fi

# Souce in get_pids().
source $P4CBIN/ps_functions.sh || exit 1

# Add and override values from p4_vars
export P4LOG=$LOGS/p4p.log
export P4P_FLAGS="-d -p $PROXY_PORT -r $P4PCACHE -t $PROXY_TARGET -e 3072 -L $P4LOG"

case "$1" in
   start)
      echo "Starting ${P4PBIN} ${P4P_FLAGS}"
      ${P4PBIN} ${P4P_FLAGS}
   ;;

   status)
      p4p_pids=$(get_pids "$P4PBIN")
      if [[ -n "$p4p_pids" ]]; then
         echo "${P4PBIN} is running as pids: $p4p_pids."
         exit 0
      else
         echo "${P4PBIN} is NOT running."
         exit 1
      fi
   ;;

   stop)
      p4p_pids=$(get_pids "$P4PBIN")

      if [[ -n "$p4p_pids" ]]; then
         while [[ -n "$p4p_pids" ]]; do
            echo "Shutting down ${P4PBIN} pids: $p4p_pids."
            kill $p4p_pids 2>&1 | $GREP -v -i "No such"
            sleep 1
            p4p_pids=$(get_pids "$P4PBIN")
         done
         echo "${P4PBIN} stopped."
         exit 0
      else
         echo "${P4PBIN} was NOT running."
         exit 1
      fi
   ;;
   restart)
      $0 stop
      $0 start
   ;;
   *)
      echo "Usage: $0 {start|stop|status|restart}"
      exit 1
   ;;
esac
# Change User Description Committed
#2 15789 alan_petersen Merging latest revision
#1 15465 alan_petersen Merging using sdp_alan_petersen
//guest/perforce_software/sdp/dev/Server/Unix/p4/common/bin/p4p_base
#4 13906 C. Thomas Tyler Normalized P4INSTANCE to SDP_INSTANCE to get Unix/Windows
implementations in sync.

Reasons:
1. Things that interact with SDP in both Unix and Windows
environments shoudn't have to account for this obscure
SDP difference between Unix and Windows.  (I came across
this doing CBD work).

2. The Windows and Unix scripts have different variable
names for defining the same concept, the SDP instance.
Unix uses P4INSTANCE, while Windows uses SDP_INSTANCE.

3. This instance tag, a data set identifier, is an SDP concept.
I prefer the SDP_INSTANCE name over P4INSTANCE, so I prpose
to normalize to SDP_INSTANCE.

4. The P4INSTANCE name makes it look like a setting that might be
recognized by the p4d itself, which it is not.  (There are other
such things such as P4SERVER that could perhaps be renamed as
a separate task; but I'm not sure we want to totally disallow
the P4 prefix for variable names. It looks too right to be wrong
in same cases, like P4BIN and P4DBIN.  That's a discussion for
another day, outside the scope of this task).

Meanwhile:
* Fixed a bug in the Windows 2013.3 upgrade script that
was referencing undefined P4INSTANCE, as the Windows
environment defined only SDP_INSTANCE.

* Had P4INSTANCE been removed completely, this change would
likely cause trouble for users doing updates for existing
SDP installations.  So, though it involves slight technical debt,
I opted to keep a redundant definition of P4INSTANCE
in p4_vars.template, with comments indicating SDP_INSTANCE should be
used in favor of P4INSTANCE, with a warning that P4INSTANCE
may go away in a future release.  This should avoid unnecessary
upgrade pain.

* In mkdirs.sh, the varialbe name was INSTANCE rather than
SDP_INSTANCE.  I changed that as well.  That required manual
change rather than sub/replace to avoid corrupting other similar
varialbe names (e.g.  MASTERINSTANCE).

This is a trivial change technically (a substitute/replace, plus
tweaks in p4_vars.template), but impacts many files.
#3 12169 Russell C. Jackson (Rusty) Updated copyright date to 2015

 Updated shell scripts to require an instance parameter to eliminate the need
 for calling p4master_run.    Python and Perl still need it since you have to set the
environment for them to run in.

 Incorporated comments from reviewers. Left the . instead of source as that seems
more common in the field and has the same functionality.
#2 10852 Domenic Base proxy script updates.
- Remove p4broker references.
- Fix "stop" command for the service to get p4p_pids instead of p4broker_pids.
#1 10638 C. Thomas Tyler Populate perforce_software-sdp-dev.
//guest/perforce_software/sdp/main/Server/Unix/p4/common/bin/p4p_base
#1 10148 C. Thomas Tyler Promoted the Perforce Server Deployment Package to The Workshop.