table of contents
LSLOCKS(8) | System Administration | LSLOCKS(8) |
NAME¶
lslocks - list local system locks
SYNOPSIS¶
lslocks [options]
DESCRIPTION¶
lslocks lists information about all the currently held file locks in a Linux system.
OPTIONS¶
-b, --bytes
By default, the unit, sizes are expressed in, is byte, and unit prefixes are in power of 2^10 (1024). Abbreviations of symbols are exhibited truncated in order to reach a better readability, by exhibiting alone the first letter of them; examples: "1 KiB" and "1 MiB" are respectively exhibited as "1 K" and "1 M", then omitting on purpose the mention "iB", which is part of these abbreviations.
-H, --list-columns
-i, --noinaccessible
-J, --json
-n, --noheadings
-o, --output list
The default list of columns may be extended if list is specified in the format +list (e.g., lslocks -o +BLOCKER).
--output-all
-p, --pid pid
-r, --raw
-u, --notruncate
-h, --help
-V, --version
OUTPUT¶
COMMAND
PID
TYPE
SIZE
INODE
MAJ:MIN
MODE
M
START
END
PATH
BLOCKER
HOLDERS
NOTES¶
The lslocks command is meant to replace the lslk(8) command, originally written by Victor A. Abell <abe@purdue.edu> and unmaintained since 2001.
"The process holding the lock" for leases, FLOCK locks, and OFD locks is a fake-concept. They are associated with the open file description on which they are acquired. With fork(2) and/or cmsg(3), multiple processes can share an open file description. So the holder process of a lease (or a lock) is not uniquely determined. lslocks shows the one of the holder processes in COMMAND and PID columns.
AUTHORS¶
Davidlohr Bueso <dave@gnu.org>
SEE ALSO¶
REPORTING BUGS¶
For bug reports, use the issue tracker at <https://github.com/util-linux/util-linux/issues>.
AVAILABILITY¶
The lslocks command is part of the util-linux package which can be downloaded from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils/util-linux/>.
2024-05-28 | util-linux 2.40.2 |