---------------------------------------------------------------------- lockers.pl (2007) ---------------------------------------------------------------------- lockers.pl and supporting documentation will be available in a day or so. Please e-mail dbloch@google.com if you would like to be notified once they're submitted. Dan ---------------------------------------------------------------------- locks.pl (2006) ---------------------------------------------------------------------- This directory contains the "locks.pl" script discussed in my presentation at the 2006 Perforce European User Conference, "Performance and Database Locking at Large Perforce Sites." The locks.pl script reports on p4 commands holding locks, which helps track down the causes of the Perforce server hanging. Notes: - locks.pl must be run on the same machine as the Perforce server. - It must either be run as same Unix user as Perforce server, or it prompts for a password to run "sudo". This is a limitation of the Linux lsof command. - At the beginning of the script there are few constants which may need to be changed for your site. - locks.pl can be run "as is" with the -d for demo mode. The reason this is considered demo mode is that if the server is hanging, the script may hang as well when it tries to execute the "p4 monitor show" command. "Production mode" involves a tiny separate Perforce server running on port 1999. The setup.sh script will set this up. You'll need to set a few constants before running this script. - locks.pl has been tested on Linux and is likely to run on other versions of Unix with minor modification. It will not run on Windows. usage: locks.pl [-dvk] -d demo mode--doesn't require separate server running -v verbose -k kill long-running "p4 integrated" and "p4 changes -i" commands The slides for the presentation are available on Perforce's web site as http://www.perforce.com/perforce/eucon2006/presentations/Google.pdf. Please e-mail comments or suggestions to dbloch@google.com. Dan Bloch Google 29-Sep-2006