ports/62378: lsof semi-broken on 5.1-RELEASE-p10
Nate Eldredge
nge at cs.hmc.edu
Thu Feb 5 09:40:12 UTC 2004
>Number: 62378
>Category: ports
>Synopsis: lsof semi-broken on 5.1-RELEASE-p10
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Feb 05 01:40:05 PST 2004
>Closed-Date:
>Last-Modified:
>Originator: Nate Eldredge
>Release: FreeBSD 5.1-RELEASE-p10 i386
>Organization:
>Environment:
System: FreeBSD mercury.lan 5.1-RELEASE-p10 FreeBSD 5.1-RELEASE-p10 #0: Fri Oct 3 19:12:00 PDT 2003 nate at mercury:/medium/obj/medium/src/sys/MERCURY i386
>Description:
Using lsof-4.70 from ports, it doesn't give very helpful information
about files in processes. For a perfectly ordinary sleep process I get
mercury# sleep 1000 < /tmp/foo &
[1] 21798
mercury# lsof -p 21798
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sleep 21798 root cwd unknown file system type: -1045301384
sleep 21798 root rtd unknown file system type: -1037192472
sleep 21798 root 0 no more information
sleep 21798 root 1 0xc1ba6168 file struct, ty=0, op=0xc03a5ce0
sleep 21798 root 2 0xc1ba6168 file struct, ty=0, op=0xc03a5ce0
The filesystem in question is ordinary UFS.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list