💾 Archived View for gemini.ctrl-c.club › ~jolek78 › blog › 2023-10-19.gmi captured on 2023-12-28 at 16:43:44. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-04)
-=-=-=-=-=-=-
___ __ ___ ____ _ __ _ ___
|_ ) \_ )__ /___/ |/ \ ___/ / _ \
/ / () / / |_ \___| | () |___| \_, /
/___\__/___|___/ |_|\__/ |_|/_/
Today, I was knee-deep in Bash scripting like there was no tomorrow. I was tackling a bunch of tasks, like updating some packages, tinkering with kernel settings, and lending a hand to a colleague with this mysterious(?) library that Red Hat decided to shuffle around with the libc package – what a puzzle...
But the real brain-twister was trying to figure out the inner workings of Zabbix and deciding which route to take to shoot a clear message over to the main server. Here's the deal: I'm supposed to do this and that, whip up a quick temp file to read some dates, grab the latest date, and make sure the whole shebang goes off without a hitch. If it does, I shoot an "OK" message over to Zabbix and clean up the old queue. If it doesn't go smoothly, you fire off a fail message to Zabbix and then reboot the script every hour using a cronjob.
The thing is, making all this happen in a script isn't a walk in the park. The real challenge is getting into the minds of the folks who wrote and tweaked this code before me. Reading someone else's code feels a bit like trying to sew a needle into a stranger's head – maybe I can figure it out, but it definitely leaves me scratching my head, especially when it's a whopping 200 and more lines long. In other words, a terminal adventure.