Return to Answer

MINIX 3 has a procfs server which provides several Linux-like components including /proc/PID/ directories. However this does not there is no /proc/PID/fd.

• Under Linux, /dev/fd is a symbolic link to /proc/self/fd.
• Under most unices (IRIX, OpenBSD, NetBSD, SCO, Solaris, …), the entries in /dev/fd are character devices. They usually appear whether the file descriptor is open or not, and entries may not be available for file descriptors above a certain number.
• Under FreeBSD and OSX, the fdescfs filesystem provides a dynamic /dev/fd directory which follows the open descriptors of the calling process. A static /dev/fd is available is /dev/fd is not mounted.
• Under OSF/1 (Tru64), /dev/fd is provided via fdfs.
• There is no /dev/fd on AIX or HP-UX.

MINIX 3 has a procfs server which provides several Linux-like components including /proc/PID/ directories. However there is no /proc/PID/fd.

• Under Linux, /dev/fd is a symbolic link to /proc/self/fd.
• Under most unices (IRIX, OpenBSD, NetBSD, SCO, Solaris, …), the entries in /dev/fd are character devices. They usually appear whether the file descriptor is open or not, and entries may not be available for file descriptors above a certain number.
• Under FreeBSD and OSX, the fdescfs filesystem provides a dynamic /dev/fd directory which follows the open descriptors of the calling process. A static /dev/fd is available if /dev/fd is not mounted.
• Under OSF/1 (Tru64), /dev/fd is provided via fdfs.
• There is no /dev/fd on AIX or HP-UX.

Lsof can't obtain path name components from the kernel name caches of the following dialects:

 

• AIX

 

Only the Linux kernel records full path names in the structures it maintains about open files; instead, most kernels convert path names to device and node number doublets and use them for subsequent file references once files have been opened.

Lsof can't obtain path name components from the kernel name caches of the following dialects:

• AIX

Only the Linux kernel records full path names in the structures it maintains about open files; instead, most kernels convert path names to device and node number doublets and use them for subsequent file references once files have been opened.

• Under Linux, /dev/fd is a symbolic link to /proc/self.
• Under most unices (IRIX, OpenBSD, NetBSD, SCO, Solaris, …), the entries in /dev/fd are character devices. They usually appear whether the file descriptor is open or not, and entries may not be available for file descriptors above a certain number.
• Under FreeBSD and OSX, the fdescfs filesystem provides a dynamic /dev/fd directory which follows the open descriptors of the calling process. A static /dev/fd is available is /dev/fd is not mounted.
• Under OSF/1 (Tru64), /dev/fd is provided via fdfs.
• There is no /dev/fd on AIX or HP-UX.

• Under Linux, /dev/fd is a symbolic link to /proc/self/fd.
• Under most unices (IRIX, OpenBSD, NetBSD, SCO, Solaris, …), the entries in /dev/fd are character devices. They usually appear whether the file descriptor is open or not, and entries may not be available for file descriptors above a certain number.
• Under FreeBSD and OSX, the fdescfs filesystem provides a dynamic /dev/fd directory which follows the open descriptors of the calling process. A static /dev/fd is available is /dev/fd is not mounted.
• Under OSF/1 (Tru64), /dev/fd is provided via fdfs.
• There is no /dev/fd on AIX or HP-UX.