lslocks - list local system locks
lslocks lists information about all the currently held file locks in a
Note that lslocks also lists OFD (Open File Description) locks,
these locks are not associated with any process (PID is -1). OFD locks are
associated with the open file description on which they are acquired. This
lock type is available since Linux 3.15, see fcntl(2) for more
Print the SIZE column in bytes rather than in a
Ignore lock files which are inaccessible for the current
Use JSON output format.
Do not print a header line.
-o, --output list
Specify which output columns to print. Use --help
to get a list of all supported columns.
The default list of columns may be extended if list is
specified in the format +list (e.g., lslocks -o +BLOCKER).
Output all available columns.
-p, --pid pid
Display only the locks held by the process with this
Use the raw output format.
Do not truncate text in columns.
Display version information and exit.
Display help text and exit.
The command name of the process holding the lock.
The process ID of the process which holds the lock or -1
Size of the locked file.
The lock’s access permissions (read, write). If
the process is blocked and waiting for the lock, then the mode is postfixed
with an '*' (asterisk).
Whether the lock is mandatory; 0 means no (meaning the
lock is only advisory), 1 means yes. (See fcntl(2)
Relative byte offset of the lock.
Ending offset of the lock.
Full path of the lock. If none is found, or there are no
permissions to read the path, it will fall back to the device’s
mountpoint and "..." is appended to the path. The path might be
truncated; use --notruncate to get the full path.
The PID of the process which blocks the lock.
The lslocks command is meant to replace the lslk(8) command,
originally written by Victor A. Abell <email@example.com> and
unmaintained since 2001.
Davidlohr Bueso <firstname.lastname@example.org>