tree 7bcacf519d0e5f13aa17df886b967d1fec8a4075
parent 17e419ec05880ac15c34186b67bc3c6f304772ff
author Googler <noreply@google.com> 1453291905 +0000
committer Lukacs Berki <lberki@google.com> 1453299059 +0000

Fix documentation of --[no]block_for_lock

The help message of this option had the effect inversed. The default
--block_for_lock setting makes the client block waiting for the lock
when needed, and the flag needs to be unset with --noblock_for_lock
to instead exit immediately.

Also rename the dummy noblock_for_lock variable to blockForLock to match
the naming convention. The variable is not used anywhere, as this class
only exists for the help messages.

--
MOS_MIGRATED_REVID=112566287