strace
mostra que o shell do GNOME está continuamente tentando ler de um soquete,
que muitas vezes não está disponível (ou não contém dados para ler):
strace -p gnome-shell-pid -e trace=recvfrom
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, "3tlrwx------. 1 me me 64 Jan 5 12:48 6 -> socket:[55696]
gnome-she 2250 hamid 6u unix 0xffff880101064000 0t0 55696 socket
gdbus 2250 5801 hamid 6u unix 0xffff880101064000 0t0 55696 socket
dconf 2250 5805 hamid 6u unix 0xffff880101064000 0t0 55696 socket
threaded- 2250 5806 hamid 6u unix 0xffff880101064000 0t0 55696 socket
JS 2250 5807 hamid 6u unix 0xffff880101064000 0t0 55696 socket
JS 2250 5808 hamid 6u unix 0xffff880101064000 0t0 55696 socket
gmain 2250 5818 hamid 6u unix 0xffff880101064000 0t0 55696 socket
strace -p gnome-shell-pid -e trace=recvfrom
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, "3tlrwx------. 1 me me 64 Jan 5 12:48 6 -> socket:[55696]
gnome-she 2250 hamid 6u unix 0xffff880101064000 0t0 55696 socket
gdbus 2250 5801 hamid 6u unix 0xffff880101064000 0t0 55696 socket
dconf 2250 5805 hamid 6u unix 0xffff880101064000 0t0 55696 socket
threaded- 2250 5806 hamid 6u unix 0xffff880101064000 0t0 55696 socket
JS 2250 5807 hamid 6u unix 0xffff880101064000 0t0 55696 socket
JS 2250 5808 hamid 6u unix 0xffff880101064000 0t0 55696 socket
gmain 2250 5818 hamid 6u unix 0xffff880101064000 0t0 55696 socket
%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%041472", 4096, 0, NULL, NULL) = 32
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%%pre%041472", 4096, 0, NULL, NULL) = 32
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvfrom(6, 0x1390a84, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
/proc/$pid/fd
mostra que 6 é um descritor de arquivo para um soquete UNIX.
Eu tentei obter informações sobre isso em /proc/$pid/net/unix
, mas parece que esse arquivo não contém informações úteis para essa finalidade.
É possível saber qual processo está do outro lado dessa conexão?
Editar:
saída de lsof | grep 55696
:
Isso significa que esse soquete é usado por threads do processo de shell do GNOME. OK, mas alguém pode dizer quais dados são enviados e recebidos por esse soquete?