# This is an example config file for the totalusers.py script. # # case_sensitive can be set to 0 or 1 with 0 indicating case insensitive operation, and # 1 indicating case sensitive. # # report_access_time can be set to 0 or 1 as well with 0 indicating do not report last access time, and # indicating to include the last access time in the report. # # The next set of lines identify the robotic users to ignore. The format is: # ROBOT|username # Just include a line like that for all of your robotic users. # # The remaining lines are the lines showing the servers to include. Each line consists of the following: # SERVER|host:port|login|SDP_INSTANCE # The SERVER word just identifies this line as a line to parse for server information. # The name:port is the standard perforce P4PORT setting for the server. The user name is a valid login. case_sensitive=0 report_access_time=1 report_email=1 ROBOT|perforce ROBOT|swarm ROBOT|build SERVER|localhost:1666|perforce|1
Released SDP 2021.1.28238 (2021/11/12).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
Renamed sample files (e.g. SiteTags.cfg) in SDP tarball tree, appending
a .sample tag, to make rsync overlay of /p4/common/config safe.
Updated related docs in mkrep.sh referring to the sample file, to improve
an error message to guide the user to find the sample file.
This is Tom's change:
Introduced new 'Unsupported' directory to clarify that some files
in the SDP are not officially supported. These files are samples for
illustration, to provide examples, or are deprecated but not yet
ready for removal from the package.
The Maintenance and many SDP triggers have been moved under here,
along with other SDP scripts and triggers.
Added comments to p4_vars indicating that it should not be edited
directly. Added reference to an optional site_global_vars file that,
if it exists, will be sourced to provide global user settings
without needing to edit p4_vars.
As an exception to the refactoring, the totalusers.py Maintenance
script will be moved to indicate that it is supported.
Removed settings to support long-sunset P4Web from supported structure.
Structure under new .../Unsupported folder is:
Samples/bin Sample scripts.
Samples/triggers Sample trigger scripts.
Samples/triggers/tests Sample trigger script tests.
Samples/broker Sample broker filter scripts.
Deprecated/triggers Deprecated triggers.
To Do in a subsequent change: Make corresponding doc changes.
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).
|#1||10148||tom_tyler||Promoted the Perforce Server Deployment Package to The Workshop.|