lsof doesn't recognize DCCP sockets

Bug #692990 reported by Erik Inge Bolsø
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lsof (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: lsof

To reproduce: start netsend listening on a DCCP socket.

$ netsend dccp receive

Do a lsof | grep netsend

knan@ip:~$ lsof | grep netsend
netsend 25588 knan cwd DIR 252,11 4096 352042 /home/bolso/ak-git/htrosbif
netsend 25588 knan rtd DIR 8,1 4096 2 /
netsend 25588 knan txt REG 8,1 94592 376294 /usr/bin/netsend
netsend 25588 knan mem REG 8,1 1572232 1562251 /lib/libc-2.11.1.so
netsend 25588 knan mem REG 8,1 534832 1561658 /lib/libm-2.11.1.so
netsend 25588 knan mem REG 8,1 136936 1561962 /lib/ld-2.11.1.so
netsend 25588 knan 0u CHR 136,1 0t0 4 /dev/pts/1
netsend 25588 knan 1u CHR 136,1 0t0 4 /dev/pts/1
netsend 25588 knan 2u CHR 136,1 0t0 4 /dev/pts/1
netsend 25588 knan 3u sock 0,6 0t0 685217 can't identify protocol

And the DCCP socket only shows up as "can't identify protocol".

I expected it to show up something like this UDPLITE example instead:

netsend 25572 knan 3u IPv4 681227 0t0 UDPLITE *:6666

knan@ip:~$ lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04

knan@ip:~$ apt-cache policy lsof
lsof:
  Installed: 4.81.dfsg.1-1build1
  Candidate: 4.81.dfsg.1-1build1

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.