From nate@cs.hmc.edu  Thu Feb  5 01:35:54 2004
Return-Path: <nate@cs.hmc.edu>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BB73F16A4CE
	for <freebsd-gnats-submit@freebsd.org>; Thu,  5 Feb 2004 01:35:54 -0800 (PST)
Received: from turing.cs.hmc.edu (turing.cs.hmc.edu [134.173.42.99])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2BB0743D31
	for <freebsd-gnats-submit@freebsd.org>; Thu,  5 Feb 2004 01:35:53 -0800 (PST)
	(envelope-from nate@cs.hmc.edu)
Received: by turing.cs.hmc.edu (Postfix, from userid 26983)
	id C8796532AA; Thu,  5 Feb 2004 01:35:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by turing.cs.hmc.edu (Postfix) with ESMTP id B8E175A917
	for <freebsd-gnats-submit@freebsd.org>; Thu,  5 Feb 2004 01:35:52 -0800 (PST)
Message-Id: <200401300633.i0U6XE0I021851@mercury.lan>
Date: Thu, 29 Jan 2004 22:33:14 -0800 (PST)
From: Nate Eldredge <nge@cs.hmc.edu>
Reply-To: Nate Eldredge <nge@cs.hmc.edu>
To: FreeBSD-gnats-submit@freebsd.org
Cc: nge@cs.hmc.edu
Subject: lsof semi-broken on 5.1-RELEASE-p10
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         62378
>Category:       ports
>Synopsis:       lsof semi-broken on 5.1-RELEASE-p10
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    obrien
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Feb 05 01:40:05 PST 2004
>Closed-Date:    Thu Dec 16 08:51:00 GMT 2004
>Last-Modified:  Thu Dec 16 08:51:00 GMT 2004
>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@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:
Responsible-Changed-From-To: freebsd-ports-bugs->obrien  
Responsible-Changed-By: krion 
Responsible-Changed-When: Thu Feb 5 01:44:59 PST 2004 
Responsible-Changed-Why:  
Over to maintainer. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=62378 

From: Cy Schubert <Cy.Schubert@komquats.com>
To: Nate Eldredge <nge@cs.hmc.edu>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: ports/62378: lsof semi-broken on 5.1-RELEASE-p10 
Date: Fri, 06 Feb 2004 22:02:32 -0800

 In message <200401300633.i0U6XE0I021851@mercury.lan>, Nate Eldredge writes:
 > 
 > >Number:         62378
 
 I've had no problems with lsof under 5.1R (when I used 5.1R) and I don't 
 have any problems with it under -CURRENT. Rebuild the port and try again.
 
 
 Cheers,
 --
 Cy Schubert <Cy.Schubert@komquats.com>        http://www.komquats.com/
 BC Government                     .                       FreeBSD UNIX
 Cy.Schubert@osg.gov.bc.ca         .                     cy@FreeBSD.org
 http://www.gov.bc.ca/             .            http://www.FreeBSD.org/
 
 

From: Nate Eldredge <nge@cs.hmc.edu>
To: Cy Schubert <Cy.Schubert@komquats.com>
Cc: Nate Eldredge <nge@cs.hmc.edu>, FreeBSD-gnats-submit@freebsd.org
Subject: Re: ports/62378: lsof semi-broken on 5.1-RELEASE-p10 
Date: Fri, 6 Feb 2004 22:30:56 -0800 (PST)

 On Fri, 6 Feb 2004, Cy Schubert wrote:
 
 > In message <200401300633.i0U6XE0I021851@mercury.lan>, Nate Eldredge writes:
 > >
 > > >Number:         62378
 >
 > I've had no problems with lsof under 5.1R (when I used 5.1R) and I don't
 > have any problems with it under -CURRENT. Rebuild the port and try again.
 
 I had rebuilt it, that was the first thing I tried.  However, I have since
 upgraded to 5.2-RELEASE-p2 and rebuilt lsof and it works now.  Thanks for
 the suggestion.
 
 -- 
 Nate Eldredge
 nge@cs.hmc.edu
State-Changed-From-To: open->closed 
State-Changed-By: edwin 
State-Changed-When: Thu Dec 16 08:50:43 GMT 2004 
State-Changed-Why:  
Issue has passed. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=62378 
>Unformatted:
