summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md8
-rw-r--r--index.md2
-rw-r--r--uptime-stats.md2
3 files changed, 5 insertions, 7 deletions
diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md
index 39f0c59c..8a39fbc1 100644
--- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md
+++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.md
@@ -33,13 +33,10 @@ Table of contents:
My auto-failover requirements
My HA solution
Only OpenBSD base installation required
- !/bin/ksh
- Race condition (e.g. script execution aborted in the middle of the previous run)
Fairly cheap and geo-redundant
Failover time and split-brain
Failover support for multiple protocols
Let's encrypt TLS certificates
- Weekly auto-failover for Let's Encrypt automation
Monitoring
Rex automation
More HA
@@ -159,7 +156,8 @@ transform () {
After the failover, the script reloads `nsd` and performs a sanity check to see if DNS still works. If not, a rollback will be performed:
```sh
-# Race condition (e.g. script execution aborted in the middle of the previous run)
+#! Race condition !#
+
if [ -f $zone_file.bak ]; then
mv $zone_file.bak $zone_file
fi
@@ -252,7 +250,7 @@ As a solution, the CRON job responsible for the DNS failover also checks for the
Which translates to:
```sh
-# Weekly auto-failover for Let's Encrypt automation
+#! Weekly auto-failover for Let's Encrypt automation !#
local -i -r week_of_the_year=$(date +%U)
if [ $(( week_of_the_year % 2 )) -eq 0 ]; then
local tmp=$master
diff --git a/index.md b/index.md
index a5cc8da9..34fe0264 100644
--- a/index.md
+++ b/index.md
@@ -1,6 +1,6 @@
# foo.zone
-> This site was generated at 2024-04-21T11:44:45+03:00 by `Gemtexter`
+> This site was generated at 2024-04-21T11:52:49+03:00 by `Gemtexter`
```
|\---/|
diff --git a/uptime-stats.md b/uptime-stats.md
index d0014c0b..be32627f 100644
--- a/uptime-stats.md
+++ b/uptime-stats.md
@@ -1,6 +1,6 @@
# My machine uptime stats
-> This site was last updated at 2024-04-21T11:44:45+03:00
+> This site was last updated at 2024-04-21T11:52:49+03:00
The following stats were collected via `uptimed` on all of my personal computers over many years and the output was generated by `guprecords`, the global uptime records stats analyser of mine.