######################################################### #### CONFIGURATION VARIABLES: CHANGE AS NEEDED #### #### #### # # Section number. Copy the entire section of configuration variables foreach # instance of Perforce and change the section number for each instance. # [INSTANCE] # ######################################## [1] server=perforce.company.com:1666 p4user=perforce passwd=password weeks=12 weeks1warn=10 weeks2warn=11 administrator=admin@company.com complain_from=PerforceReviewDaemon_1666@company.com ccadmin=none repeat=0 sleeptime=60 domain=company.com default_user_password=P@SsW0rD mailhost=mail.company.com # Use below for secure connections # mailport = 587 # mailuser and mailpass only used for secure connections. # Change mailsecure to 1 for secure connections. mailsecure=0 mailuser=myacct@gmail.com mailpass=mypass mailport=25
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#3 | 26060 | C. Thomas Tyler |
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). |
||
#2 | 16373 | C. Thomas Tyler |
Routine Merge Down to dev from main using: p4 merge -b perforce_software-sdp-dev |
||
#1 | 10638 | C. Thomas Tyler | Populate perforce_software-sdp-dev. | ||
//guest/perforce_software/sdp/main/Maintenance/maintenance.cfg | |||||
#2 | 10464 | Russell C. Jackson (Rusty) | Corrected typos and added import sys. | ||
#1 | 10148 | C. Thomas Tyler | Promoted the Perforce Server Deployment Package to The Workshop. |