michal-sapka-me

commit 597b4ece6f708840cd6a21707e674cee8ef7a5ef
parent ec63889fa1e5ed4c70abd58193005a75ad49d4d9
Author: Michał M. Sapka <michal@sapka.me>
Date:   Sun, 30 Jul 2023 19:33:00 +0200

fix: cron snippet

Diffstat:
M
content/2023/moved-to-openbsd.md
 | 
5
+++--

1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/content/2023/moved-to-openbsd.md b/content/2023/moved-to-openbsd.md
@@ -241,10 +241,10 @@ Besides adding headers, we configure TLS here, disabling weak ciphers and old TL
 Lastly, we can automate refreshing the certificate via cron(8):
 
 {{<highlight shell>}}
-0-59 0-23 * * 1 acme-client michal.sapka.me &&  rcctl reload relayd
+0~59 0~23 * * 1 acme-client michal.sapka.me &&  rcctl reload relayd
 {{</highlight>}}
 
-It looks almost like a normal cron. The "0-59" and "0-29" parts are unique to OpenBSD: Cron(8) will evenly split all tasks between specified time boxes so that no two jobs run simultaneously.
+It looks almost like a normal cron. The "0~59" and "0~29" parts are unique to OpenBSD: Cron(8) will evenly split all tasks between specified time boxes so that no two jobs run simultaneously.
 
 We now have created a fully working web server without any 3rd party packages. All OpenBSD provided, all secure, all simple, all cool as ice.
 
@@ -304,4 +304,5 @@ What are my next steps? It looks like OpenBSD much better supports the hardware 
 ## Updates
 
 2023-07-28: remove wrong information abot PF.
+2023-07-30: fix invalid cron format