#!/bin/bash #============================================================================== # Copyright and license info is available in the LICENSE file included with # the Server Deployment Package (SDP), and also available online: # https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/LICENSE #------------------------------------------------------------------------------ # # Perforce server 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 export TMP=$P4TMP if [[ ! -x $P4DBIN ]] ; then echo "$P4DBIN is not executable." exit 2; 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 # See how we were called. case "$1" in force_start) echo "Starting $P4DBIN $P4D_FLAGS" $P4DBIN $P4D_FLAGS ;; start) if [[ -r $P4ROOT/db.domain ]]; then PreflightLog=${P4TMP}/preflight.log $P4DBIN -r $P4ROOT -xvU > $PreflightLog 2>&1 ExitCode=$? echo EXIT_CODE=$ExitCode >> $PreflightLog if [[ $ExitCode -ne 0 ]]; then echo -e "\nError: DB check with 'p4d -xvU' failed. Database integrity is in question. Please Contact Perforce Support (support@perforce.com). The force_start option is availble, but not recommended. See:\n" cat $PreflightLog /bin/rm -f $PreflightLog exit 1 else /bin/rm -f $PreflightLog fi fi echo "Starting $P4DBIN $P4D_FLAGS" $P4DBIN $P4D_FLAGS ;; status) $P4BIN -p $P4PORT -u $P4USER info -s ;; stop) echo -n "Shutting down $P4DBIN: " if [[ "${P4REPLICA}" == "FALSE" ]]; then $P4BIN -p $P4PORT -u $P4USER login < /p4/common/bin/adminpass fi $P4BIN -p $P4PORT -u $P4USER admin stop sleep 5 $P4BIN -p $P4PORT info > /dev/null 2>&1 ExitCode=$? if [[ $ExitCode -eq 0 ]]; then echo -e "\nError: Server shutdown failed." exit 1 else exit 0 fi ;; restart) $0 stop $0 start ;; *) echo "Usage: $0 {start|stop|status|restart|force_start}" exit 1 ;; esac exit 0
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#6 | 25113 | Robert Cowham | Merge latest changes from dev | ||
#5 | 23430 | Robert Cowham | Merge in changes from dev | ||
#4 | 23205 | Robert Cowham | Merged all changes from dev to test | ||
#3 | 22477 | Robert Cowham | Bring latest dev changes into test | ||
#2 | 20726 | Robert Cowham | Catch up from dev | ||
#1 | 18586 | Robert Cowham | Branching using cowhamr.sdp.dev | ||
//guest/perforce_software/sdp/dev/Server/Unix/p4/common/bin/p4d_base | |||||
#8 | 17281 | Robert Cowham |
When stopping, send error to /dev/null Remove tabs #review @rjackson @ttyler ttyler: Looks good! |
||
#7 | 16335 | C. Thomas Tyler |
Routine Merge Down to dev from main using: p4 merge -b perforce_software-sdp-dev |
||
#6 | 16029 | C. Thomas Tyler |
Routine merge to dev from main using: p4 merge -b perforce_software-sdp-dev |
||
#5 | 15778 | C. Thomas Tyler | Routine Merge Down to dev from main. | ||
#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 | 11493 | Russell C. Jackson (Rusty) | Removed echo for Preflight Check. | ||
#1 | 10638 | C. Thomas Tyler | Populate perforce_software-sdp-dev. | ||
//guest/perforce_software/sdp/main/Server/Unix/p4/common/bin/p4d_base | |||||
#1 | 10148 | C. Thomas Tyler | Promoted the Perforce Server Deployment Package to The Workshop. |