Bug 126419

Summary: lsof doesn't behave properly with path-less sockets
Product: Red Hat Enterprise Linux 3 Reporter: Need Real Name <lsof>
Component: lsofAssignee: Jakub Jelinek <jakub>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0Keywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 4.72-1 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-07-30 16:59:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2004-06-21 13:23:20 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; 
NPLv1.5)

Description of problem:
lsof will not show locked files for sockets unless the full path is 
given.

WITHOUT FULL PATH:
 [root@box /]# cd /tmp/
 [root@box tmp]# lsof jd_sockV4
 [root@box tmp]#

WITH FULL PATH:
 [root@box /]# lsof /tmp/jd_sockV4
 COMMAND  PID USER   FD   TYPE     DEVICE SIZE NODE NAME
 jserver 1225  wnn    3u  unix 0xf787c700      1829 /tmp/jd_sockV4

WITH NON-EXISTANT FILE:
 # lsof non-existing-file
 lsof: status error on doesnt-exist: No such file or directory

Version-Release number of selected component (if applicable):
Comment 1 Need Real Name 2004-07-30 10:45:41 UTC 
Any news on this?