I built a small Linux CLI tool called witr (Why Is This Running?).
The idea came from a situation most of us have hit: you log into a machine, see a process or port running, and immediately wonder why it exists, who started it, and what is keeping it alive right now.
witr traces a process, service, or port back to its origin and responsibility chain and explains it in a way that’s quick to read, especially when you’re debugging under pressure.
This is v0.1.0. It’s intentionally small and focused. Feedback, criticism, and edge cases are very welcome.
pranshuparmar•1mo ago
Happy to answer questions or adjust direction based on feedback.
dcminter•1mo ago
---
Edit: Ah, ok, I slightly misunderstood - skimmed the README too quickly. I thought it was also explaining what the process did :D Still a clever tool, but thought it went a step further.
Perhaps you should add that though - combine Man page output with a database of known processes that run on various Linux systems and a mechanism for contributing PRs to extend that database...? Unlesss it's just me that often wants to know "what the fsck does /tmp/hax0r/deeploysketchyd actually do?" :P
filterfish•1mo ago
If you could look it up using APT/dpkg first, that would be lovely :-)
ajb•1mo ago
darrenf•1mo ago
https://www.man7.org/linux/man-pages/man1/whatis.1.html
pranshuparmar•1mo ago
scrame•1mo ago
New tools are always welcome, and having a purpose to explain a purpose seems like a good pitch.
pranshuparmar•1mo ago