HN Explorer

17 comments

[ 3.5 ms ] story [ 17.9 ms ] thread
MayeulC
I might be missing something here, but shouldn't the graph be directed (processes opening fifos in read-only mode, or even unidirectional pipes like on Linux)? Or is it something impossible to query with lsof?

It otherwise is a very neat graphical overview of the state of a system!

zevv
afaik that info is not available from lsof, but I'm open to suggestions if there is more sensible data to extract from the output.
cryptonector
That info is available. If a pipe fd is open for reading, then that's the fd for reading...
aidos
Cool! More interesting, I didn’t know the dot utility for creating the visual representations of the graphs. I can think of a bunch of uses for that.
loeg
dot (part of graphviz) is super handy.
xmichael99
Thank you for referencing the package dot is in!
TimWolla
systemd-analyze(1) supports dot(1) output to plot dependencies between units:

Quoting from the man page:

    EXAMPLES FOR DOT
       Example 1. Plots all dependencies of any unit whose name starts with "avahi-daemon"

           $ systemd-analyze dot 'avahi-daemon.*' | dot -Tsvg > avahi.svg
                 $ eog avahi.svg

       Example 2. Plots the dependencies between all known target units

           systemd-analyze dot --to-pattern='*.target' --from-pattern='*.target' | dot -Tsvg > targets.svg
           $ eog targets.svg
fsniper
I wish I had this when I started my career. I would have well slept more.
bpchaps
Hah, I wrote something very, very similar to this recently. The problem I eventually had with it was that lsof wasn't always installed on the hosts I was working with. So, it turned into a script to parse through /proc and other nonsense.

https://github.com/red-bin/lsofer/blob/master/lsofer.sh

(wish I could paste the graphing code, but it's code I wrote at my company.)

sgroppino
Now we just need to combine this with lstopo.
jakeogh
Cool! What's it's license?
zevv
Just added the LICENSE file, 2 clause BSD