Protections: super group ServiceUsers * //... super user __P4USER__ * //...
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #1 | 31751 | C. Thomas Tyler | p4 stream convertsparse | ||
| //p4-sdp/dev/Server/setup/protect.p4t | |||||
| #1 | 31397 | C. Thomas Tyler | Populate -b SDP_Classic_to_Streams -s //guest/perforce_software/sdp/...@31368. | ||
| //guest/perforce_software/sdp/dev/Server/setup/protect.p4t | |||||
| #2 | 29928 | C. Thomas Tyler |
Fixed issue with Protections being assigned to hard-coded rather than configurable value on a fresh, greenfield install. |
||
| #1 | 29849 | C. Thomas Tyler |
Updates to configure_new_server.sh: * Added logic to start service so this script can now be run if the service is down at the start. * The 'security' configurable is now set to 4 (was unset). * Enhanced error handling. * Added logic to more fully initialize a new/empty server: - Create perforce P4USER (if there is only a single user on the system). - Create Automation group. - Initialize basic Protections. Updates to configure_new_server.bat: * Added logic to start service so this script can now be run if the service is down at the start. * The 'security' configurable is now set to 4 (was unset). In mkdirs.cfg, change the default password to one good enough to be used with `security=4`. #review-29850 |
||