#!/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 #------------------------------------------------------------------------------ # P4Web base init script # Do nothing unless $SDP_INSTANCE is defined. export SDP_INSTANCE=${1:-Unset} if [[ $SDP_INSTANCE == Unset ]]; then echo -e "\nError: The SDP_INSTANCE is not defined.\n." exit 1 fi # Load SDP controlled shell environment. source /p4/common/bin/p4_vars "$SDP_INSTANCE" if [[ $? -ne 0 ]]; then echo -e "\nError: Failed to load SDP environment for instance $SDP_INSTANCE.\n" exit 1 fi source $P4CBIN/ps_functions.sh if [[ $? -ne 0 ]]; then echo -e "\nError: Failed to load SDP ps_functions.sh lib.\n" exit 1 fi if [[ $(id -u) -ne 0 ]]; then echo "$0 can only be run as root." exit 1 fi if [[ ! -x $P4WEBBIN ]]; then echo -e "\nError: $P4WEBBIN is not executable." exit 2; fi if [[ ! -x $P4WEBBIN ]]; then echo "$P4WEBBIN is not executable." exit 2; fi # See how we were called. case "${2:-status}" in start) echo "Starting $P4WEBBIN." $P4WEBBIN $P4WEBARGS & ;; status) p4web_pids=$(get_pids $P4WEBBIN) if [[ -n "$p4web_pids" ]]; then echo "${P4WEBBIN} is running as pids: $p4web_pids." exit 0 else echo "${P4WEBBIN} is NOT running." exit 1 fi ;; stop) p4web_pids=$(get_pids $P4WEBBIN) if [[ -n "$p4web_pids" ]]; then while [[ -n "$p4web_pids" ]]; do echo "Shutting down ${P4WEBBIN} pids: $p4web_pids." kill $p4web_pids 2>&1 | $GREP -v -i "No such" sleep 1 p4web_pids=$(get_pids $P4WEBBIN) done echo "${P4WEBBIN} stopped." exit 0 else echo "${P4WEBBIN} was NOT running." exit 1 fi ;; restart) $0 $SDP_INSTANCE stop $0 $SDP_INSTANCE start ;; *) echo -e "\nUsage: $0 SDP_INSTANCE {start|stop|status|restart}\n" exit 1 ;; esac exit 0
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#2 | 22838 | Russell C. Jackson (Rusty) | More SDP clean up/simplification. | ||
#1 | 22693 | Russell C. Jackson (Rusty) |
Branched a Unix only version of the SDP. Removed extra items to create a cleaner tree. Moved a few items around to make more sense without Windows in the mix. |
||
//guest/perforce_software/sdp/dev/Server/Unix/p4/common/bin/p4web_base | |||||
#9 | 20559 | C. Thomas Tyler |
Fixed recent regression with 'restart' option in init scripts; they now need to pass in the SDP_INSTANCE parameter. Also corrected usage messages. |
||
#8 | 20491 | C. Thomas Tyler |
Fixed an environment insulation bug in init scripts. More testing (and thinking) revealed that the only way to truly provide a guarantee of insulation from user-set defaults in ~perforce/.bashrc (etc.) is to pass SDP_INSTANCE as a parameter to the *_base scripts, so that the instance name is explicitly passed into the su/exec call (when run as root). This change also includes minor cleanup in init scripts and *_base scripts. |
||
#7 | 20448 | C. Thomas Tyler |
Fixed env bug seen when running init scripts as root. Updated *_base scripts and *_init script templates to a new standard. Goals: 1. Init scripts that use corresponding *_base scripts are minimized so that do nothing more than set SDP_INSTANCE and then call the corresponding *_base script. 2. The 'su' commands always pass $* instead of $1, deferring all processing to the *_base script. 3. The shell environment is now guaranteeds to have the same results regardless of whether it is called as 'root' or as the defined OSUSER. 4. The p4_vars file is always sourced exactly once. Two calls to 'source p4_vars' appear in some cases, one immediatley before the su/exec call, and another after the after the 'su/exec'. Only one or the other is sourced. 5. All init scripts have a reasonably consistent usage message. 6. All init scripts accept a 'status' argument. This change fixes a bug where 'p4broker_N_init status' run as the 'perforce' user would report many pids unrelated to Perforce if run as root, e.g. doing 'service p4broker_N_init status'. This also eliminates a potential issue where the 'perforce' user might source a p4_vars with a default instance in ~/.profile or ~/.bashrc, thus invalidating the instance specified when the user ran the init script as root. |
||
#6 | 20429 | C. Thomas Tyler |
Updated p4web_base and p4ftpd_base with a check that they are running as root, with error if not (as those init scripts must be run as root; they can't run as perforce). |
||
#5 | 16029 | C. Thomas Tyler |
Routine merge to dev from main using: p4 merge -b perforce_software-sdp-dev |
||
#4 | 15778 | C. Thomas Tyler | Routine Merge Down to dev from main. | ||
#3 | 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. |
||
#2 | 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. |
||
#1 | 10638 | C. Thomas Tyler | Populate perforce_software-sdp-dev. | ||
//guest/perforce_software/sdp/main/Server/Unix/p4/common/bin/p4web_base | |||||
#1 | 10148 | C. Thomas Tyler | Promoted the Perforce Server Deployment Package to The Workshop. |