Description of problem: lsof 4.78 release 6 displays a '0t0' string on TCP lines in field 'SIZE/OFF', where this used to be empty space (or maybe a tab) in release 3 Version-Release number of selected component (if applicable): 4.78 R6 How reproducible: Do an lsof on a system with lsof 4.78 release 6 and compare to an lsof on a similar system with release 3 In our specific case we were monitoring some java processes by user jboss: lsof -p $(ps -fu jboss | awk '/java/ {print $2}') Actual results: [just some of the releveant lines:] java 3541 jboss 343u IPv6 1636161 0t0 TCP b1.example.com:8093->10.2.3.4:cecsvc (ESTABLISHED) java 3541 jboss 344u IPv6 1636217 0t0 TCP b1.example.com:8093->10.2.3.4:hl7 (ESTABLISHED) java 3541 jboss 345u IPv6 1636219 0t0 TCP b1.example.com:8093->10.2.3.4:tclprodebugger (ESTABLISHED) Expected results: [output from a different unpatched server:] java 26241 jboss 203u IPv6 45414608 TCP b1.example.com:8093->b1.example.com:56387 (ESTABLISHED) java 26241 jboss 204u IPv6 45412471 TCP b1.example.com:8093->10.2.3.4:37743 (ESTABLISHED) java 26241 jboss 205u IPv6 45414610 TCP b1.example.com:8093->b1.example.com:56388 (ESTABLISHED) Additional info:
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
No clue what you are expecting from me.