## Confessions of a Distracted Linux Coder: How "Port Already in Use" Turned into Heimdall
Hey everyone,
You know those moments when you're deep in code on Linux and suddenly…
**"Why can't I delete this file?"**
**"Which damn process is holding port 8080?"**
**"Wait, who just opened that socket?"**
One minute you're writing a function, the next you're running `lsof`, `ss`, `fuser`, `ps aux | grep`, `journalctl -u`, and `iotop` like a madman.
By the time you fix the tiny problem, you’ve completely forgotten what you were actually working on.
**"What was I doing again?"** 😅
Or worse — that paranoid feeling creeps in:
"Is everything okay? Why is systemd-journald eating CPU?
Who is scraping my disk like it's a frying pan?
Why are the modem lights blinking non-stop?
Who is sending all these packets?!"
And the worst one:
"Did that innocent little package I just installed silently start talking to the outside world without telling me?"
Switching between five different TUIs and terminals just to answer basic questions gets exhausting.
I got tired of it.
So… I ended up going down the rabbit hole.
What started as a quick hack to find "who's using this port" slowly grew into something bigger.
And because I can't help myself, I added way too many icons to make it feel a little more fun 😄
Ladies and gentlemen, meet **Heimdall** – my little terminal watchdog that's still very much in its crawling baby stage.
https://github.com/sunels/heimdall
It's nowhere near perfect, but it already saves me a surprising amount of time every day.
If you ever feel the same frustration, give it a try.
Feedback, suggestions, or even a tiny PR would genuinely make me happy.
Thanks for reading,
.png)
No comments:
Post a Comment