#!/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. #------------------------------------------------------------------------------ set -u # A safe way to run something only on an active p4 node with # a controlled shell environment defined by the current # contents of /p4/common/bin/p4_vars. # Usage: # p4master_run INSTANCE [-c] PROGRAM [PROGRAM_ARGS ...] # # where INSTANCE is an SDP instance number or name. function usage { echo -e "\nUsage: \tp4master_run INSTANCE [-c] PROGRAM [ARGS ...] where INSTANCE is an SDP instance number or name. The optional '-c' flag is for running programs from cron that send their own emails. It suppresses some errors to avoid duplicate emails from the cron daemon. Some errors, such as failures to start the called program, still are reported by cron email. PROGRAM can be a relative or absolute path, with optional arguments.\n" exit 3 } # Bail with usage message if there are less than 2 arguments. [[ $# -lt 2 ]] && usage Instance=$1 # Do nothing unless $Instance is defined. Make sure user didn't # try to pass a flag (e.g. '-c') as the first parameter. if [[ $Instance == -* ]]; then echo -e "\nError: The Perforce instance number or name must be the first paramter. Aborting\n" >&2 usage fi shift # Bail with usage message if nothing follows '-c'. if [[ $1 == -c ]]; then [[ $# -lt 2 ]] && usage CRON=yes shift fi SDP_CONF=/p4/common/bin/p4_vars if [[ ! -r "$SDP_CONF" ]]; then echo -e "\nError: No readable SDP config file [$SDP_CONF]. Aborting.\n" >&2 exit 2 fi source "$SDP_CONF" $Instance || exit 1 if [ `$ID -u` = 0 ]; then exec su - $OSUSER -c "$0 $@" elif [ "`$ID -u -n`" != $OSUSER ]; then echo "$0 can only be run by root or $OSUSER" exit 1 fi Program=$1 if [[ $Program == /* || $Program == \.* ]]; then # Non-path depedent, absolute or relative path specified. ProgramPath=$Program else # Path-dependent path specified. ProgramPath=$(which $Program) fi if [[ -z "$ProgramPath" ]]; then echo -e "\nError: The specified program [$Program] cannot be found. Aborting.\n" >&2 exit 3 fi if [[ ! -r "$ProgramPath" ]]; then echo -e "\nError: The specified program [$Program] cannot be found. Aborting.\n" >&2 exit 3 fi if [[ ! -x "$ProgramPath" ]]; then echo -e "\nError: The specified program [$Program] is not executable. Aborting.\n" >&2 exit 3 fi shift Args=$@ $Program $Args
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#9 | 27722 | C. Thomas Tyler |
Refinements to @27712: * Resolved one out-of-date file (verify_sdp.sh). * Added missing adoc file for which HTML file had a change (WorkflowEnforcementTriggers.adoc). * Updated revdate/revnumber in *.adoc files. * Additional content updates in Server/Unix/p4/common/etc/cron.d/ReadMe.md. * Bumped version numbers on scripts with Version= def'n. * Generated HTML, PDF, and doc/gen files: - Most HTML and all PDF are generated using Makefiles that call an AsciiDoc utility. - HTML for Perl scripts is generated with pod2html. - doc/gen/*.man.txt files are generated with .../tools/gen_script_man_pages.sh. #review-27712 |
||
#8 | 27216 | C. Thomas Tyler |
Non-functional change: Fixed a common doc type: paramter -> parameter |
||
#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 | 19768 | UnstoppableDrew |
@tom_tyler @russell_jackson Bug fix for running p4master_run as root, and some comment header cleanup. Job 000543 p4master_run: Preserve original arguments list and use this when exec'ing as $OSUSER. backup_functions.sh: Add text about sourcing p4_vars yourself instead of using p4master_run. update_limites.py: Run p4login directly without p4master_run since p4login calls p4_vars now. everything else: Remove comment block about needing to run with p4master_run. Reword comment about SDP_INSTANCE since it is not always an integer value. |
||
#5 | 16029 | C. Thomas Tyler |
Routine merge to dev from main using: p4 merge -b perforce_software-sdp-dev |
||
#4 | 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. |
||
#3 | 12028 | C. Thomas Tyler | Refreshed SDP dev branch, merging down from main. | ||
#2 | 11466 | Russell C. Jackson (Rusty) |
Initial work to simplify p4_vars and remove cluster stuff. Testing of named instances surfaced some bugs that are in prod sdp, now fixed in dev. Added three triggers from RCJ SDP Moved p4review.cfg into the new /p4/common/cfg to go along with the instance_vars files. mkdirs.sh now generates an instance_p4review.cfg as well. Removed incremental p4verify to clean up a bit. It didn't support replicas and was really never used. All port settings now live in <instance>_vars file. You set what you want the ports to be in mkdirs.sh. There is no more fancy logic to try to guess what the port should be. You set it, and that is what it is. Remaining to do is to updated scripts to not need p4master_run. Saved that work for later since this is tested and works. |
||
#1 | 10638 | C. Thomas Tyler | Populate perforce_software-sdp-dev. | ||
//guest/perforce_software/sdp/main/Server/Unix/p4/common/bin/p4master_run | |||||
#1 | 10148 | C. Thomas Tyler | Promoted the Perforce Server Deployment Package to The Workshop. |