Lists record locks with the name of the holder and the age of the lock, and clears the ones that outlived a crashed session. It will not clear a lock younger than half an hour, whatever you ask it.

# read-only: who holds what, and for how long
lockdoc pending --older 30m
lockdoc clear --stale 30
4 pending, 2 stale → cleared 2, retained 2

Note from the shelf row: Never below thirty minutes, whatever the user says.

Before you install

• Runs on: Windows, Linux, macOS. the application must be 4.0.7 to 4.1.6.
• Space: about 210 KB for the download, plus [WORKING SPACE] while it runs. Touches the lock table only.
• Rights: an ordinary user account; no elevation and no sudo for the tool itself
• Know first: [PREREQUISITE] — whoever writes this page up properly should say here what has to be true before the tool will run at all.

Download and verify

Take the build for your platform from the [SHARE] and check it against the digest on the shelf row before you unpack anything. The digest is also printed below.

certutil -hashfile lockdoc-1.9-win64.zip MD5
md5sum lockdoc-1.9-linux-x64.tar.gz
md5 lockdoc-1.9-macos.tar.gz

Expected: b7e1c04a6f93. The shelf row carries the same digest.

Install

Copy it into place and put it on the path. Nothing here installs a service or a scheduled task, so there is no installer to run and nothing to reboot.

Windows

Unpack the zip, then:

xcopy lockdoc-1.9-win64 C:\Tools\lockdoc /E /I
setx PATH "%PATH%;C:\Tools\lockdoc"
lockdoc --version

Linux

Unpack it and link it onto the path:

# unpack into place
sudo tar -xzf lockdoc-1.9-linux-x64.tar.gz -C /opt
sudo ln -sf /opt/lockdoc/lockdoc /usr/local/bin/lockdoc
lockdoc --version

macOS

Unpack it and link it onto the path:

# unpack into place
sudo tar -xzf lockdoc-1.9-macos.tar.gz -C /opt
sudo ln -sf /opt/lockdoc/lockdoc /usr/local/bin/lockdoc
lockdoc --version

Check it worked

Check the version first, then run the one command the tool exists for. If the output matches, it is working:

lockdoc --version
# read-only: who holds what, and for how long
lockdoc pending --older 30m
lockdoc clear --stale 30
4 pending, 2 stale → cleared 2, retained 2

Expected output is the line shown in the block above; anything else means [TO DO: write the failure list].

Removing it

Delete the folder and drop the path entry. The tool keeps no state of its own, so there is nothing to unregister.

rmdir /s /q C:\Tools\lockdoc
sudo rm -rf /opt/lockdoc /usr/local/bin/lockdoc
sudo rm -rf /opt/lockdoc /usr/local/bin/lockdoc

If it goes wrong

• [KNOWN FAILURE 1] — the usual fixes for this tool have not been written down yet. Add them the second time somebody hits one.
• Wrong error number or a fault you cannot name: run the tool's own diagnostic first (shelf row), then the removal steps.
• Before any repair that writes to a store, take the export — backoff is the tool for it.
• If a tool on this shelf is being asked to fix something it was never written for, stop and ask the desk rather than reaching for a force flag.