diff options
| author | Paul Buetow <paul@buetow.org> | 2025-07-13 16:51:47 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2025-07-13 16:51:47 +0300 |
| commit | 2196a00cfefc7cdb1cd110d4cba1b67c8d2fc2bd (patch) | |
| tree | ce3bb78390ad9b9a44b7e8e4706f8558d6913f75 /gemfeed | |
| parent | 937bc35df74d46968471cc1355e04c9f90898dc8 (diff) | |
Update content for html
Diffstat (limited to 'gemfeed')
| -rw-r--r-- | gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html | 4 | ||||
| -rw-r--r-- | gemfeed/atom.xml | 6 |
2 files changed, 5 insertions, 5 deletions
diff --git a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html index 327407c9..4cb061bd 100644 --- a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html +++ b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.html @@ -61,7 +61,7 @@ <li>⇢ ⇢ <a href='#carp-control-script-for-clean-failover'>CARP Control Script for Clean Failover</a></li> <li>⇢ ⇢ <a href='#carp-management-script'>CARP Management Script</a></li> <li>⇢ ⇢ <a href='#automatic-failback-after-reboot'>Automatic Failback After Reboot</a></li> -<li>⇢ <a href='#client-configuration-for-stunnel'>Client Configuration for Stunnel</a></li> +<li>⇢ <a href='#client-configuration-for-nfs-via-stunnel'>Client Configuration for NFS via Stunnel</a></li> <li>⇢ ⇢ <a href='#configuring-rocky-linux-clients-r0-r1-r2'>Configuring Rocky Linux Clients (<span class='inlinecode'>r0</span>, <span class='inlinecode'>r1</span>, <span class='inlinecode'>r2</span>)</a></li> <li>⇢ ⇢ <a href='#testing-nfs-mount-with-stunnel'>Testing NFS Mount with Stunnel</a></li> <li>⇢ ⇢ <a href='#testing-carp-failover-with-mounted-clients-and-stale-file-handles'>Testing CARP Failover with mounted clients and stale file handles:</a></li> @@ -1484,7 +1484,7 @@ CARP state on re0 (vhid <font color="#000000">1</font>): MASTER </ul><br /> <span>This ensures <span class='inlinecode'>f0</span> automatically resumes its role as primary storage server after any reboot, while providing administrative control when needed.</span><br /> <br /> -<h2 style='display: inline' id='client-configuration-for-stunnel'>Client Configuration for Stunnel</h2><br /> +<h2 style='display: inline' id='client-configuration-for-nfs-via-stunnel'>Client Configuration for NFS via Stunnel</h2><br /> <br /> <span>To mount NFS shares with stunnel encryption, clients must install and configure stunnel using their client certificates.</span><br /> <br /> diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index cda6264c..5488b4e1 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"> - <updated>2025-07-13T16:45:56+03:00</updated> + <updated>2025-07-13T16:50:30+03:00</updated> <title>foo.zone feed</title> <subtitle>To be in the .zone!</subtitle> <link href="https://foo.zone/gemfeed/atom.xml" rel="self" /> @@ -68,7 +68,7 @@ <li>⇢ ⇢ <a href='#carp-control-script-for-clean-failover'>CARP Control Script for Clean Failover</a></li> <li>⇢ ⇢ <a href='#carp-management-script'>CARP Management Script</a></li> <li>⇢ ⇢ <a href='#automatic-failback-after-reboot'>Automatic Failback After Reboot</a></li> -<li>⇢ <a href='#client-configuration-for-stunnel'>Client Configuration for Stunnel</a></li> +<li>⇢ <a href='#client-configuration-for-nfs-via-stunnel'>Client Configuration for NFS via Stunnel</a></li> <li>⇢ ⇢ <a href='#configuring-rocky-linux-clients-r0-r1-r2'>Configuring Rocky Linux Clients (<span class='inlinecode'>r0</span>, <span class='inlinecode'>r1</span>, <span class='inlinecode'>r2</span>)</a></li> <li>⇢ ⇢ <a href='#testing-nfs-mount-with-stunnel'>Testing NFS Mount with Stunnel</a></li> <li>⇢ ⇢ <a href='#testing-carp-failover-with-mounted-clients-and-stale-file-handles'>Testing CARP Failover with mounted clients and stale file handles:</a></li> @@ -1491,7 +1491,7 @@ CARP state on re0 (vhid <font color="#000000">1</font>): MASTER </ul><br /> <span>This ensures <span class='inlinecode'>f0</span> automatically resumes its role as primary storage server after any reboot, while providing administrative control when needed.</span><br /> <br /> -<h2 style='display: inline' id='client-configuration-for-stunnel'>Client Configuration for Stunnel</h2><br /> +<h2 style='display: inline' id='client-configuration-for-nfs-via-stunnel'>Client Configuration for NFS via Stunnel</h2><br /> <br /> <span>To mount NFS shares with stunnel encryption, clients must install and configure stunnel using their client certificates.</span><br /> <br /> |