# Note: We use REPL_MAILFROM rather than REPL_MAILTO, since # REPL_MAILFROM is guaranteed to be a single email address, # where REPL_MAILTO might be a list of addresses. Only a # single email address is accepted here. User: REPL_P4USER Email: REPL_MAILFROM FullName: Perforce Admin Type: standard
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #1 | 25533 | tom_tyler |
Copied updated and new files from SDP into the new HMS "overlay" structure. A 'p4 copy' was done in all cases, so files in this change match what they did in the SDP. Corresponding files in the SDP are to be deleted. Some files will need modification to adapt to the new HMS structure, e.g. the 'setup' tree. |
||
| //guest/perforce_software/sdp/dev/Server/Unix/setup/hms/superuser.user.p4t | |||||
| #2 | 25114 | tom_tyler |
Fixed bug where an extra user named REPL_OSER was created on the 'hms'
server, and the 'perforce' user was created wrongly. |
||
| #1 | 21294 | tom_tyler | Merged down hms dev work. | ||
| //guest/perforce_software/sdp/dev/Server/Unix/setup/hms/perforce.user.p4s | |||||
| #1 | 21103 | tom_tyler | Merge down to dev from main. | ||
| //guest/perforce_software/sdp/main/Server/Unix/setup/hms/perforce.user.p4s | |||||
| #1 | 21081 | tom_tyler |
Added preliminary files in support of automation of the HMS Tight Ship installation. The key file here hs hms_ts_setup.sh, which is currently a 'doc only' script that documents what it is intended to do, although it doesn't currently do anything that affects data. The '-h' and '-man' flags work to convey their intent. This also contains various spec files to be used in the actual implementation. Bypassing pre-commit review since this is only adding new 'doc only' code, not active software. #review-21082 |
||