список открытых файлов (list open files)
LSOF PERMISSIONS THAT AFFECT DEVICE CACHE FILE ACCESS
Two permissions of the lsof executable affect its ability to
access device cache files. The permissions are set by the local
system administrator when lsof is installed.
The first and rarer permission is setuid-root. It comes into
effect when lsof is executed; its effective UID is then root,
while its real (i.e., that of the logged-on user) UID is not.
The lsof distribution recommends that versions for these dialects
run setuid-root.
HP-UX 11.11 and 11.23
Linux
The second and more common permission is setgid. It comes into
effect when the effective group IDentification number (GID) of
the lsof process is set to one that can access kernel memory
devices - e.g., ``kmem'', ``sys'', or ``system''.
An lsof process that has setgid permission usually surrenders the
permission after it has accessed the kernel memory devices. When
it does that, lsof can allow more liberal device cache path
formations. The lsof distribution recommends that versions for
these dialects run setgid and be allowed to surrender setgid
permission.
AIX 5.[12] and 5.3-ML1
Apple Darwin 7.x Power Macintosh systems
FreeBSD 4.x, 4.1x, 5.x and [6789].x for x86-based systems
FreeBSD 5.x, [6789].x and 1[012].8for Alpha, AMD64 and Sparc64
based systems
HP-UX 11.00
NetBSD 1.[456], 2.x and 3.x for Alpha, x86, and SPARC-based
systems
NEXTSTEP 3.[13] for NEXTSTEP architectures
OpenBSD 2.[89] and 3.[0-9] for x86-based systems
OPENSTEP 4.x
SCO OpenServer Release 5.0.6 for x86-based systems
SCO|Caldera UnixWare 7.1.4 for x86-based systems
Solaris 2.6, 8, 9 and 10
Tru64 UNIX 5.1
(Note: lsof for AIX 5L and above needs setuid-root permission if
its -X option is used.)
Lsof for these dialects does not support a device cache, so the
permissions given to the executable don't apply to the device
cache file.
Linux
