Closed AiyionPrime closed 3 years ago
One option would be to specify a list of fastd status sockets to check.
This could be a stat
, or even an open
call like in software.fastd.version.
Another way to go would be subprocess with a px grep.
The first has the drawback of intrducing yet another configparameter, as status sockets are not placed at a fixed directory iirc?
in hanover we put them under /var/run/fastd*.socket
.
found a cleaner approach similar to the second, using psutil.
... Which has the drawback of adding a dependency.
This one is related to #66 and hasn't bothered me much since now, but is there a way we could determine the state of fastd a little more dynamic? I'd even vote for some
ps
greppery if we could get rid of https://github.com/ffnord/mesh-announce/blob/2736f7b835d68aea2315264c4b8418469e9b2832/providers/nodeinfo/software/fastd/enabled.py#L5Has somebody ideas how to implement this better?