| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #2 | 16543 | Matt Attaway | Update P4DCTL with code from 15.2 and reorg files | ||
| #1 | 8907 | Matt Attaway |
Branch Tony Smith's p4dctl tool into perforce_software area p4dctl is a tool that helps admins to manage multiple Perforce servers. This tool is used by the Perforce Linux packages to help manage servers. |
||
| //guest/tony_smith/perforce/p4dctl/src/parsesupp.cpp | |||||
| #1 | 8093 | Tony Smith |
Make p4dctl support including configuration files from a specified path. This change allows it to support including from both files and directories. e.g. include /path/to/file.conf include /path/to/dir A common use of this might be something like: include /etc/p4d.d |
||
| //guest/tony_smith/perforce/p4dctl/src/parsesupp.c | |||||
| #1 | 5945 | Tony Smith |
Release p4dctl, a program for starting/stopping Perforce services on Unix operating systems. Similar to, and developed in concert with, Sven Erik Knop's p4dcfg. For example: p4dctl start -a Can start multiple P4D, P4P, P4Web, or P4FTP servers in one easy command line. It can be executed by root, or by the 'owners' of the configured services and it maintains pidfiles no matter who uses it (so they remain accurate). An init script using p4dctl will typically just use: p4dctl start -a p4dctl stop -a p4dctl restart -a And check the exit status. |
||