Since Linux 5.2, there is a new metric in the hood: Pressure Stall Information (PSI). Currently it supplies 3 ciritical metrics from kernel: CPU, IO and memory. You can find the values simply by looking to files under /proc/pressure folder. I am not going to try explaining it in detail, since this page already does that pretty good. I've found it way better than just the load metric because of granularity.
We were using a handmade Python backup application at work. While it works, it was not practical and breaking from time to time. In that case we had to stare at the code for half an hour and ask to the single person in the company who understands its "way of doing things" eventually. So I started to look for a "better backup tool". Stumbled upon a lot of alternatives, but decided to use Restic for multiple good reasons:
I've been planning to create my own knowledgebase for a while. I believe knowledge kept secret worth nothing. Also if you're working with open source tools, it's extremely important to help others. But never found any tool convenient enough, since everything requires some weird formats to make it presentable. My notes are in Markdown format, which is pretty convenient once you set up your editor for it. I've discovered vimwiki very late, and there is an awesome helper tool for it to support Markdown -> HTML conversion.
I've been using KDE for very long time (except when it lost all of its stability in the beginning of KDE4). Lately, since everything was going smooth with my NixOS setup, I've decided to remember my good old window manager days and try out some tiling WM options. After all I am already using an extension for KWin to have tiling feature. First tried dwm since my extension tries to replicate its layouts anyway, but patching the C code for every change wasn't for me.
In Debian, package upgrades trigger restart of the related service. After I've restarted all my postgresql nodes (1 primary + 2 hot standby) at the same time, I've realized one of the secondaries were not able to process WAL files any further. Checking the logs gave me an idea: 2019-07-09 13:20:32 UTC [25065-1] postgres@[local] FATAL: the database system is starting up gzip: stdin: unexpected end of file ERROR: Remote 'barman get-wal' command has failed!
When you go to a repository, first thing you look is a README. I realized this might be the case for some of the local folders (since I am currently re-organizing). So I've defined a simple concept to keep track what's happening on a foler. The rules are simple, just create a dotfile (so it would be hidden) under any directory you feel like needs explanation: .folder-README. Afterwards add a simple check like following to your shell configuration (for me it is .
I sometimes see questions like "Which certificate should I get?" or "I'm planning to get X, does it worth the price/work I invest?" in forums/reddit. Most of the time I also can't answer it, because I am not really sure if my RHCE certificate helped me or not. It will also expire few months later. And after giving some thought, I've decided to let it. Even though I understand "It will be a clear sign about how well I know what I am doing" theory behind it, if I were hiring someone technical, a certificate wouldn't slightly change my idea in any way.
I've been playing with Nixops lately. Wanted to deploy a nixos server to Vultr (since it's my current provider). Nixos ISO was in the list of ISO's you can attach. After a small search, I've found a cool script on GitHub to bootstrap the environment properly. Yet, I wanted it to be encrypted (yeah I know, entering password on boot..) and forked it to make securestrap ¯_(ツ)_/¯ I like how easy the whole declarative stuff is.
When I was new to Linux, I settled on Debian unstable after trying some of the popular distros. Ironically it was so stable that I got bored and switched to Gentoo. And for about a year, since our infrastructure is largely consist of Debian on my workplace, I was using Debian again. And here I am, craving for another toy to play with. Since I like to learn new stuff by getting my hands dirty, I looked up for something new.
If you're working on multiple computers/servers, managing your personal config files is a hard task. And as a sysadmin, I need my settings to be as global as possible. Many people are uploading their dotfiles under GitHub or some other public place. This has downsides, at least for me, since one can easily have private information embedded inside these files. Some people synchronizes these files to cloud services like Dropbox.