From: Christian Goeschel Ndjomouo Date: Tue, 2 Sep 2025 16:58:06 +0000 (-0400) Subject: lslocks: (man) add LSLOCKS_COLUMNS description in new ENVIRONMENT section X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=def89ba6d0daf48b18e88a3d81f75489b1bb8110;p=thirdparty%2Futil-linux.git lslocks: (man) add LSLOCKS_COLUMNS description in new ENVIRONMENT section Signed-off-by: Christian Goeschel Ndjomouo --- diff --git a/misc-utils/lslocks.8.adoc b/misc-utils/lslocks.8.adoc index 743f275f3..2944e3afa 100644 --- a/misc-utils/lslocks.8.adoc +++ b/misc-utils/lslocks.8.adoc @@ -112,6 +112,11 @@ 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. +== ENVIRONMENT + +LSLOCKS_COLUMNS=:: +Specifies a comma-separated list of output columns to print. All columns listed by *--list-columns* can be used. + == NOTES The *lslocks* command is meant to replace the *lslk*(8) command, originally written by mailto:abe@purdue.edu[Victor A. Abell] and unmaintained since 2001. @@ -123,9 +128,12 @@ description on which they are acquired. With *fork*(2) and/or 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. +The default output is subject to change. So whenever possible, you should avoid using default output in your scripts. + == AUTHORS mailto:dave@gnu.org[Davidlohr Bueso] +mailto:cgoesc2@wgu.edu[Christian Goeschel Ndjomouo] == SEE ALSO