Differences between version 2 and predecessor to the previous major change of lsof(8).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Tuesday, June 4, 2002 12:31:15 am | by perry | Revert |
| Older page: | version 1 | Last edited on Tuesday, June 4, 2002 12:31:15 am | by perry | Revert |
@@ -64,13 +64,13 @@
Linux 2.0.3[[2346], 2.1.x, and 2.2.x for Intel-based systems
NetBSD 1.[[234] for Intel and SPARC-based systems
NEXTSTEP 3.[[13] for NEXTSTEP architectures
OpenBSD 2.[[0123456] for Intel-based systems
-OpenStep 4.x
+!
OpenStep 4.x
Reliant UNIX 5.4[[34] for Pyramid systems
-SCO OpenServer Release 3.0 and 5..[[0245] for Intel-based
+SCO !
OpenServer Release 3.0 and 5..[[0245] for Intel-based
systems
-SCO UnixWare 2.1.[[123] and 7[[[[.].1] for Intel-based systems
+SCO !
UnixWare 2.1.[[123] and 7[[[[.].1] for Intel-based systems
Sequent PTX 2.1.9, 4.2.[[13], 4.[[34], and 4.4[[.124] for
Sequent systems
Solaris 2.5.1, 2.6, 7, 8 BETA, and 8 BETA-Refresh
SunOS 4.1.x
@@ -1356,11 +1356,11 @@
w__ for a write lock on part of the file;__
W__ for a write lock on the entire file;__
u__ for a read and write lock of any length;__
U__ for a lock of unknown type;__
-x__ for an SCO OpenServer Xenix lock on part of the
+x__ for an SCO !
OpenServer Xenix lock on part of the
file;__
-X__ for an SCO OpenServer Xenix lock on the entire
+X__ for an SCO !
OpenServer Xenix lock on the entire
file;
space if there is no lock.
@@ -1874,9 +1874,9 @@
or a stream character device name, followed by ``-
-or ``STR:'' followed by the SCO OpenServer stream device and
+or ``STR:'' followed by the SCO !
OpenServer stream device and
module names, separated by ``-
or the SunOS current working or root directory path
@@ -1915,9 +1915,9 @@
or ``rd=
-or ``clone ''n'':/dev/event'' for SCO OpenServer file
+or ``clone ''n'':/dev/event'' for SCO !
OpenServer file
clones of the ''/dev/event'' device, where ''n'' is
the minor device number of the file;
@@ -2265,9 +2265,9 @@
''Lsof's'' use of the kernel name cache to identify the
paths of files can lead it to report incorrect components
under some circumstances. This can happen when the kernel
name cache uses device and node number as a key (e.g., Linux
-and SCO OpenServer) and a key on a rapidly changing file
+and SCO !
OpenServer) and a key on a rapidly changing file
system is reused. If the UNIX dialect's kernel doesn't purge
the name cache entry for a file when it is unlinked,
''lsof'' may find a reference to the wrong entry in the
cache. The ''00FAQ'' file of the ''lsof'' distribution
@@ -2288,10 +2288,10 @@
NEXTSTEP
OpenBSD
PTX
Reliant UNIX
-SCO OpenServer
-SCO UnixWare
+SCO !
OpenServer
+SCO !
UnixWare
Solaris
SunOS
Ultrix
''Lsof'' can't report path name components for these dialects:
@@ -2401,11 +2401,11 @@
NetBSD 1.[[234] for Intel and SPARC-based systems
NEXTSTEP 3.[[13] for NEXTSTEP architectures
OpenBSD 2.[[0123456] for Intel-based systems
RISC/os 4.52 for MIPS R2000-based systems
-SCO OpenServer Release 3.0 and 5..[[0245] for Intel-based
+SCO !
OpenServer Release 3.0 and 5..[[0245] for Intel-based
systems
-SCO UnixWare 2.1.[[123] and 7[[[[.].1] for Intel-based systems
+SCO !
UnixWare 2.1.[[123] and 7[[[[.].1] for Intel-based systems
Sequent PTX 2.1.9, 4.2.[[13], 4.[[34], and 4.4.[[12]
Solaris 2.5, 2.5.1, and 2.[[67]
SunOS 4.1.x
Ultrix 4.2
@@ -2756,9 +2756,9 @@
process, file descriptor, file device number, and file inode
number for each file of each process, use:
-lsof -FpcfDi
+lsof -!
FpcfDi
To list the files at descriptors 1 and 3 of every process
running the ''lsof'' command for login ID ``abe'' every
@@ -2831,9 +2831,9 @@
The support for ''/proc'' file systems is available only
for BSD, DEC OSF/1, Digital UNIX, and Tru64 UNIX dialects,
Linux, and dialects derived from SYSV R4 - e.g., FreeBSD,
-NetBSD, OpenBSD, Solaris, UnixWare.
+NetBSD, OpenBSD, Solaris, !
UnixWare.
Some ''/proc'' file items - device number, inode number,
and file size - are unavailable in some dialects. Searching
