Date: Sat, 9 Mar 1996 07:44:57 -0700 From: Sean Kelly <kelly@fsl.noaa.gov> To: FreeBSD-gnats-submit@freebsd.org Subject: bin/1070: /usr/bin/fstat doesn't display open, active pure text Message-ID: <199603091444.HAA03571@rosemary.fsl.noaa.gov> Resent-Message-ID: <199603091450.GAA29344@freefall.freebsd.org>
index | next in thread | raw e-mail
>Number: 1070
>Category: bin
>Synopsis: /usr/bin/fstat doesn't display open, active pure text
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Mar 9 06:50:01 PST 1996
>Last-Modified:
>Originator: Sean Kelly <kelly@fsl.noaa.gov>
>Organization:
Forecast Systems Laboratory
>Release: FreeBSD 2.1-STABLE i386
>Environment:
FreeBSD 2.1 installed via anon FTP in January '96. Fairly
stock machine, as hosts go. More info avail on request.
>Description:
The fstat man page claims it'll display active pure text
inodes for running processes. Under the FD column, it shows
the file number in the per-process open file table or one of
the following special names: wd, for current working
directory; tr, for kernel trace file; root, for root inode;
and text for pure text inode.
After 1000 runs of fstat looking at a busy system, the `text'
entry never appeared. Not necessarily proof, but an inductive
argument is within reach.
>How-To-Repeat:
Run fstat | grep text and see no output until you're blue in
the face.
>Fix:
Don't really know. fstat.c has some special handling for the
CDIR, TRACE, and RDIR entries but none for the text. That
might be it, but it also just might expect the text entry (-1)
to appear in filedesc table.
>Audit-Trail:
>Unformatted:
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603091444.HAA03571>