[[!meta copyright="Copyright © 2010, 2013 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] We don't have a `lsof` tool. Perhaps we could cook something with having a look at which ports are open at the moment (as [[`portinfo`|hurd/portinfo]] does, for example)? # IRC, freenode, #hurd, 2013-10-16 braunr: there's something I've been working on, it's not yet finished but usable http://paste.debian.net/58266/ it graphs port usage it's a bit heavy on the dependency-side though... but is it able to link rights from different ipc spaces ? no what do you mean exactly? know that send right 123 in task 1 refers to receive right 321 in task 2 basically, lsof i'm not sure it's possible right now, and that's what we'd really need does the kernel hand out this information? ^ right, I'm not sure it's possible either but a graph maker in less than 300 is cute :) 300 lines* well, it leverages pymatplotlib or something, it needs half of the pythonverse ;) lsof and pmap and two tools we really lack on the hurd what does portinfo --translate=PID do? i guess it asks proc so that ports that refer to task actually give useful info hml no doesn't make sense to give a pid in this case teythoon: looks like it does what we talked about :) teythoon: the output looks a bit weird anyway, i think we need to look at the code to be sure braunr: this is what aptitude update looks like: https://teythoon.cryptobitch.de/portmonitor/aptitude_portmonitor.svg