From 6a8bd13a159aa3d6880143b79c9d9ad4dd2beace Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 21 Apr 2024 11:53:02 +0300 Subject: Update content for gemtext --- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi | 8 +++----- gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl | 5 +++-- gemfeed/atom.xml | 10 ++++------ index.gmi | 2 +- uptime-stats.gmi | 2 +- 5 files changed, 12 insertions(+), 15 deletions(-) diff --git a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi index 679fa362..a442b59a 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi @@ -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/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl index 71133853..f922799a 100644 --- a/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl +++ b/gemfeed/2024-04-01-KISS-high-availability-with-OpenBSD.gmi.tpl @@ -143,7 +143,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 @@ -236,7 +237,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/gemfeed/atom.xml b/gemfeed/atom.xml index d1503b37..8763cb06 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2024-04-21T11:44:45+03:00 + 2024-04-21T11:52:49+03:00 foo.zone feed To be in the .zone! @@ -53,13 +53,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 @@ -192,7 +189,8 @@ http://www.gnu.org/software/src-highlite --> by Lorenzo Bettini http://www.lorenzobettini.it http://www.gnu.org/software/src-highlite --> -
# 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
@@ -289,7 +287,7 @@ echo "Failover of zone $zone to $MASTER completed"
 by Lorenzo Bettini
 http://www.lorenzobettini.it
 http://www.gnu.org/software/src-highlite -->
-
# 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.gmi b/index.gmi
index 9d83a3bd..eb74640e 100644
--- a/index.gmi
+++ b/index.gmi
@@ -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.gmi b/uptime-stats.gmi
index e0b9bb27..58247183 100644
--- a/uptime-stats.gmi
+++ b/uptime-stats.gmi
@@ -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.
 
-- 
cgit v1.2.3