
Deadlock_Client acquires and releases two remote mutexes.  By default,
Deadlock_Client uses tokenA and tokenB as names for token A and token
B respectively.  The order of operations is as follows:

acquire A
acquire B
release B
release A

The user can set via the command line, the names used for tokens A and
B.  By running two deadlock_clients, the user can create deadlock
situations.  For instance, in one window, run:

% ./deadlock_client -a tokenA -b tokenB -r 100

while in another window run

% ./deadlock_client -a tokenB -b tokenA -r 100

(-r specifies the number of times to perform the order of operations.)

