No Android, #ls -l 15843/fd fornece a seguinte saída,
lrwx------ u0_a179 u0_a179 2015-05-28 11:58 90 -> socket:[193728]
lrwx------ u0_a179 u0_a179 2015-05-28 11:58 91 -> socket:[193729]
lrwx------ u0_a179 u0_a179 2015-05-28 11:58 92 -> socket:[192748]
lrwx------ u0_a179 u0_a179 2015-05-28 11:58 93 -> socket:[193730]
lrwx------ u0_a179 u0_a179 2015-05-28 11:58 94 -> socket:[193440]
lrwx------ u0_a179 u0_a179 2015-05-28 11:58 95 -> socket:[192749]
lrwx------ u0_a179 u0_a179 2015-05-28 11:58 96 -> socket:[192750]
lrwx------ u0_a179 u0_a179 2015-05-28 11:58 97 -> socket:[192751]
lrwx------ u0_a179 u0_a179 2015-05-28 11:58 98 -> socket:[193441]
lrwx------ u0_a179 u0_a179 2015-05-28 11:58 99 -> socket:[193442]
Agora tentei #readlink /proc/15843/fd/99 , mas ele imprime socket:[193442] novamente.
Também tentou #grep 193442 /proc/net/unix imprime a seguir,
00000000: 00000003 00000000 00000000 0001 03 193442
Agora, como obter o nome do arquivo deste inode de soquete?