- #!/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
- # p4login generates a login ticket for the SDP super user. It is called
- # from cron scripts, and so does not normally generate output to stdout or
- # stderr.
- #
- # Normally output (stdout and stderr) is logged in $LOGS/p4login.log,
- # unless unless SDP_INSTANCE isn't defined, in which case it bails
- # immediately.
- #
- # An exit code of 0 indicates a valid login ticket exists, while a
- # non-zero exit code indicates a failure to login.
- export SDP_INSTANCE=${SDP_INSTANCE:-Undefined}
- declare -i SDP_ALWAYS_LOGIN=${SDP_ALWAYS_LOGIN:-1}
- declare DateFormat='%a %Y-%m-%d %H:%M:%S %Z'
- declare Cmd=
- function bail () { echo -e "\nError: ${1:-Unknown Error}"; exit ${2:-1}; }
- [[ $SDP_INSTANCE == Undefined ]] && bail "Error: SDP_INSTANCE not defined."
- declare TicketExpiration=$($P4BIN -ztag -F %TicketExpiration% -p $P4PORT -u $P4USER login -s 2>/dev/null)
- declare Log=$LOGS/p4login.log
- echo "$(date +'%a %Y-%m-%d %H:%M:%S %Z'): Checking login status." > $Log
- if [[ $TicketExpiration =~ [0-9]+ ]]; then
- # A 'long-term' ticket is one that expires more than a month (31 days + 1 second) from now.
- if [[ $TicketExpiration -ge 2678401 ]]; then
- echo "$(date +'%a %Y-%m-%d %H:%M:%S %Z'): Verified: User $P4USER logged into $P4PORT with a long-term ticket. Login not required." >> $Log
- if [[ $SDP_ALWAYS_LOGIN -eq 1 ]]; then
- echo "Doing login anyway as SDP_ALWAYS_LOGIN is enabled." >> $Log
- Cmd="$P4BIN -p $P4PORT -u $P4USER -s login -a"
- echo Running: $Cmd >> $Log
- $Cmd < /p4/common/bin/adminpass >> $Log 2>&1
- fi
- exit 0
- else
- echo "$(date +'%a %Y-%m-%d %H:%M:%S %Z'): Warning: User $P4USER logged into $P4PORT with a short-term ticket. Attempting to extend." >> $Log
- Cmd="$P4BIN -p $P4PORT -u $P4USER -s login -a"
- echo Running: $Cmd >> $ Log
- $Cmd < /p4/common/bin/adminpass >> $Log 2>&1
- exit $?
- fi
- else
- echo "$(date +'%a %Y-%m-%d %H:%M:%S %Z'): Warning: User $P4USER is not logged into $P4PORT. Attempting to login." >> $Log
- Cmd="$P4BIN -p $P4PORT -u $P4USER -s login -a"
- echo Running: $Cmd >> $Log
- $Cmd < /p4/common/bin/adminpass >> $Log 2>&1
- exit $?
- fi
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#2 | 15789 | alan_petersen | Merging latest revision | 9 years ago | |
#1 | 15465 | alan_petersen | Merging using sdp_alan_petersen | 9 years ago | |
//guest/perforce_software/sdp/dev/Server/Unix/p4/common/bin/p4login | |||||
#3 | 13906 | C. Thomas Tyler | Normalized P4INSTANCE to SDP_INSTANCE to get Unix/Windows implementations in sync. Rea...sons: 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. « |
10 years ago | |
#2 | 12169 | Russell C. Jackson (Rusty) | Updated copyright date to 2015 Updated shell scripts to require an instance para...meter 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. « |
10 years ago | |
#1 | 10638 | C. Thomas Tyler | Populate perforce_software-sdp-dev. | 10 years ago | |
//guest/perforce_software/sdp/main/Server/Unix/p4/common/bin/p4login | |||||
#1 | 10148 | C. Thomas Tyler | Promoted the Perforce Server Deployment Package to The Workshop. | 10 years ago |