Moving applications into an entirely containerized deployment, such as OpenShift or Kubernetes, requires care and attention. One aspect of both that is often overlooked is scheduled jobs, or cron jobs. ⏰ Cron jobs in OpenShift allow you to run certain containers on a regular basis and execute certain applications or scripts in those containers. You can use them to trigger GitLab CI pipelines, run certain housekeeping tasks in web applications, or run backups.
I have a CyberPower CP1350AVRLCD under my desk at home and I use it to run my computer, monitors, speakers, and a lamp. My new computer is a little more power hungry than my old one since I just moved to to a Ryzen 3700x and Nvidia GeForce 2060 and I like to keep tabs on how much energy it is consuming. Some power supplies offer a monitoring interface where you can watch your power consumption in real time, but I’m not willing to spend that much money.
I found myself stuck in a particularly nasty situation a few weeks ago where I had two git branches with some commits that were mixed up. Some commits destined for a branch called development ended up in master. To make matters worse, development was rebased on top of master and the history was obviously mangled. My goal was to find out which commits existed in development but didn’t exist anywhere in master.
I try to keep up with the latest kernel update from kernel.org, but parsing through the output can be a pain if there are a lot of changes taking place. Here’s a handy one-liner to make it easier to read: wget –quiet -O - http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-188.8.131.52 | grep -A 4 ^commit | grep -B 1 "^–" | grep -v "^–" It should give you some output like this: Linux 184.108.40.206 ext4: Fix potential fiemap deadlock (mmap_sem vs.