New blog. Or, more exactly, new blog software.
I moved this blog from Serendipity to Hugo.
New blog. Or, more exactly, new blog software.
I moved this blog from Serendipity to Hugo.
On my Mac, one of the annoying “features” is when the Mac screensaver comes on, the device eventually goes to sleep, and it disconnects the network. Which in turn timeouts services like Slack or Google, because these services keep a network connection open at all times. When waking up the device, I often have to login again into all the services, even though the device is just sitting in my working room on the desk all day and night. Very annoying.
I suppose it’s one of these things where Apple thinks they know better how users want their device to behave.
Sometimes I have to extract Exif information from images, mostly the GPS coordinates. The coordinates coming raw from the images are not very helpful. Let’s look at a picture I took today:
Ran into a curios problem while updating the GitHub Actions Workflow for a project:
If you use GitHub Actions to run Workflows and tests, you might have spotted this warning recently:
If you use GitHub Actions to run Workflows and tests, you might have spotted this warning recently:
Every time I peek into the webserver logfiles, I find quite a few 404 requests trying to figure out if certain exploits exist on this server. Now I get that these are automated attempts, and the number of requests coming from one IP show that they try several different exploits and path names. Nevertheless I thought that I don’t need this in my log, and on my webserver. fail2ban for the rescue.
My problem: sometimes I forget to review published interviews for a talk.
I publish a weekly interview series, the “PostgreSQL Person of the Week” interviews. The data lives in a big spreadsheet, which has several sub-sheets.
When I rolled out my new Icinga2 installation, and added disk checks for all laptops, I ran into a small problem: there is a fuse mountpoint for logged in users which only the user can read. Apparently it has something to do with Flatpack.
I’m using Icinga2 for a long time, but recently installed a new system and using Director for the first time. I know how to configure notifications in Icinga2 config files, but getting them working in Director (with Director options only) is a bit of a challenge.
Here is a step-by-step to get simple mail notifications working. From there it should be easier to configure more advanced notifications.