#!/usr/local/bin/python #------------------------------------------------------------------------------ # Copyright (c) Perforce Software, Inc., 2007-2014. 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. #------------------------------------------------------------------------------ """ Usage: python protect_groups.py remove_groups.txt p4.protect This script will drop all lines in the protect tabel that have a group referenced from the file groups.txt passed into the script. The list of groups to drop is passed in as the first parameter and the protect table is passed in as the 2nd parameter. remove_groups.txt is generated using protect_groups.py - See that script for details. Run "p4 protect -o > p4.protect" to generate the protections table. You can redirect the output of this script to a file called new.p4.protect and then you can compare the original p4.protect and the new.p4.protect. If everything looks okay, you can update the protections table by running: p4 protect -i < new.p4.protect """ import os import re import string import sys p4groups =  groups = open( sys.argv, "r" ) protect = open( sys.argv, "r" ) for group in groups.readlines(): group = group.rstrip() group = group.lower() p4groups.append( group ) for line in protect.readlines(): line = line.rstrip() origline = line line = line.lower() match = re.match(".*group (.*) \* .*", line) if (match != None): if match.group(1).lower() in p4groups: continue else: print(origline) else: print(origline) groups.close() protect.close()
This supercedes review-24715.
Bringing over recent bug fixes and code clean up from Rusty Jackson's local branch.
Adds an edge maintenance script to unload clients on edge servers.
Automated setting up maintenance.cfg from mkdirs.cfg settings.
Cleaned up sdputils.py - It had a logic bug, and fixed all scripts based on changes.
== Merge Details ==
Merge strategy: All the fixes to Maintenance scripts were brought in, but not the changes to active them in crontab that would enable them.
Rusty's original change had crontab changes to call maintenance scripts, and also calls to 'p4 unlock -x' as a workround to p4d bugs related to orphanged locks on edge servers. Those bugs are already fixed. Also, adding anything new to cron requires a test suite addition and doc updates. So changes to the template.crontab.combined were ignored. However, a new file was added to the Maintenace folder, sample_cron_entries.txt, to make it easy for folks to see those changes.
Rusty's original change had mkdirs.sh changes to generate maintenance.cfg. This change was enhanced during the merge. Rather than overwriting maintenance.cfg (potentially blowing away configuration for other instances), a new section for the new instance is appended to maintenance.cfg when 'mkdirs.sh <instance>' is run.
Future considerations: Before adding anything from Maintenance to cron, we need to do the following:
* Have mkdirs.sh install the Maintenance folder to the as-deployed structure under /p4/common, i.e. to /p4/common/maintenance, for HMS management compliance.
* Add tests and docs for each script called (directly or indirectly).
Routine merge down to dev from main using:
p4 merge -b perforce_software-sdp-dev
Routine merge to dev from main using:
p4 merge -b perforce_software-sdp-dev
Updated to use /usr/bin/env python
Added workshop header.
Changed cfg to config.
|#2||11464||russell_jackson||Current maintenance scripts.|
|#1||10148||tom_tyler||Promoted the Perforce Server Deployment Package to The Workshop.|