LSLOCKS(8) LSLOCKS(8) lslocks - lslocks [] lslocks Linux. -b, --bytes , . , , , , 2^10 (1024). ; : <<1 >> <<1 >> <<1 K>> <<1 M>>, <<>>, . -H, --list-columns List the available columns, use with --json or --raw to get output in machine-readable format. -i, --noinaccessible , . -J, --json B JSON. -n, --noheadings . -o, --output , . --help, . , + (, lslocks -o +BLOCKER) --output-all . -p, --pid pid , pid. -r, --raw . -u, --notruncate . -h, --help . -V, --version . COMMAND , . PID . TYPE ; LEASE ( fcntl(2)), FLOCK ( flock(2)), POSIX ( fcntl(2) lockf(3)) OFDLCK ( fcntl(2)). SIZE . INODE inode. MAJ:MIN , :. MODE (, ). , <<*>> (). M '; 0 <<>> ( , ), 1 <<>>. (. fcntl(2).) START . END . PATH . , <<...>> . ; --notruncate, . BLOCKER PID , . HOLDERS The holder(s) of the lock. The format of the holder is PID,COMMAND,FD. If a lock is an open file description-oriented lock, there can be more than one holder for the lock. See the NOTES below. lslocks lslk(8), Victor A. Abell 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. Davidlohr Bueso flock(1), fcntl(2), lockf(3) lslocks util-linux, Linux . util-linux 2.41 2025-03-29 LSLOCKS(8)