summaryrefslogtreecommitdiff
path: root/open_issues/lsof.mdwn
blob: 2651932d918568b208afac0e3c59b60048ac1dd4 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
[[!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

    <teythoon> braunr: there's something I've been working on, it's not yet
      finished but usable
    <teythoon> http://paste.debian.net/58266/
    <teythoon> it graphs port usage
    <teythoon> it's a bit heavy on the dependency-side though...
    <braunr> but
    <braunr> is it able to link rights from different ipc spaces ?
    <teythoon> no
    <teythoon> what do you mean exactly?
    <braunr> know that send right 123 in task 1 refers to receive right 321 in
      task 2
    <braunr> basically, lsof
    <braunr> i'm not sure it's possible right now, and that's what we'd really
      need
    <teythoon> does the kernel hand out this information?
    <braunr> ^
    <teythoon> right, I'm not sure it's possible either
    <braunr> but a graph maker in less than 300 is cute :)
    <braunr> 300 lines*
    <teythoon> well, it leverages pymatplotlib or something, it needs half of
      the pythonverse ;)
    <braunr> lsof and pmap and two tools we really lack on the hurd
    <teythoon> what does portinfo --translate=PID do?
    <braunr> i guess it asks proc so that ports that refer to task actually
      give useful info
    <braunr> hml
    <braunr> no
    <braunr> doesn't make sense to give a pid in this case
    <braunr> teythoon: looks like it does what we talked about
    <teythoon> :)
    <braunr> teythoon: the output looks a bit weird anyway, i think we need to
      look at the code to be sure
    <teythoon> braunr: this is what aptitude update looks like:
      https://teythoon.cryptobitch.de/portmonitor/aptitude_portmonitor.svg