Search
5 results for “OGSH”
-
@OGSH No there was one clear master, but every time I stopped the process there would be no failover. If I stop the process and then restarted #keepalived , then it would fail over.. I think. I thought it would be in real time, but maybe that's not how it works. It was also the priority thing plus the weight thing threw me off. Couldn't find a good example of it either.
-
I was timing two simultaneous runs of my #incus container hot-copies across my lan today to two different servers.
I am wondering if the time difference is storage-driven or CPU driven. Both are to NVMe-backed zpools but one is Gen 3 (#Kingston) and the other is Gen 4 (#Sabrent). It's over a #10G network but even so, I wouldn't really expect storage or cpu to be a "bottleneck" here as I thought the network would be the weak link by miles (even at 10G). I find this a little interesting.
-
It's (re-)build time for me, as I prepare to make some overly complicated and certainly overdue changes to my self-hosting setup. #Supermicro #H12 #EPYC #7F52 #Sabrent
This is part of a plan to replace a remote laptop that I use to store backups that have been more important to me than they ever should be. I'm retiring an ancient device and will replace it with a "low power" 1st-gen Epyc server that I use for local backups, and my new local backup is going to be, well, "somewhat upgraded".
-
I started to make my planned transition this weekend - one server now running #debian12 vs Ubuntu 22.04. I had nothing against #Ubuntu but #redhat showed me that community software is the way to go. One down, more to go. #UbuntuSnaps are now a thing of my past too.
-