From a337a522775562fb9fc9f60e31b190af78494043 Mon Sep 17 00:00:00 2001 From: Solene Rapenne Date: Sun, 10 Oct 2021 20:43:14 +0200 Subject: [PATCH] typo fixed from pamela@ thanks! --- issues/issue-2/10_HEADLINES.html | 2 +- issues/issue-2/20_CURRENT.html | 2 +- issues/issue-2/35_TIPS.html | 2 +- issues/issue-2/90_SOCIALMEDIA.html | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/issues/issue-2/10_HEADLINES.html b/issues/issue-2/10_HEADLINES.html index ae1ed03..2d1658b 100644 --- a/issues/issue-2/10_HEADLINES.html +++ b/issues/issue-2/10_HEADLINES.html @@ -3,6 +3,6 @@ diff --git a/issues/issue-2/20_CURRENT.html b/issues/issue-2/20_CURRENT.html index 37857cc..6dc177f 100644 --- a/issues/issue-2/20_CURRENT.html +++ b/issues/issue-2/20_CURRENT.html @@ -9,7 +9,7 @@
  • xterm has unveil
  • base gcc removed on amd64
  • bsd-reconfig to have a KARL compatible modified kernel
    • -
  • new dhcpleased and resolvd superseeding dhclient (now default for new installs). After upgrade you can switch to it: replace dhcp by autoconf in your network hostname.if file then enable and start the two services
    • +
  • new dhcpleased and resolvd superseding dhclient (now default for new installs). After upgrade you can switch to it: replace dhcp by autoconf in your network hostname.if file then enable and start the two services
  • performance improvements for heavy loads on many cores
    • diff --git a/issues/issue-2/35_TIPS.html b/issues/issue-2/35_TIPS.html index 8997337..b1cb578 100644 --- a/issues/issue-2/35_TIPS.html +++ b/issues/issue-2/35_TIPS.html @@ -3,6 +3,6 @@

    Shell tips

    OpenBSD 7.0 comes with a new utility named timeout to run a command and stop it after an user defined time. The is available for full information. While it was possible to achieve this in shell using a child process sleeping for some time and stopping the main process if it wasn't finished yet, timeout makes this job very easy. -One simple real world use case would be a lazy site-to-site synchronization using a rsync job run every night when the Internet uplink can be fully used and stop it right before people will need the network. Such a scenario can be done with timeout 8h rsync -a /data/ remote:/data/ and started from a cron job at 00h00. In this case rsync would run at midnight and timeout would stop it at 8h00 if the job is not finished. +One simple real world use case would be a lazy site-to-site synchronization using a rsync job run every night when the Internet uplink can be fully used and stopped right before people will need the network. Such a scenario can be done with timeout 8h rsync -a /data/ remote:/data/ and started from a cron job at 00h00. In this case rsync would run at midnight and timeout would stop it at 8h00 if the job is not finished.

    diff --git a/issues/issue-2/90_SOCIALMEDIA.html b/issues/issue-2/90_SOCIALMEDIA.html index a736bc9..c6f4b74 100644 --- a/issues/issue-2/90_SOCIALMEDIA.html +++ b/issues/issue-2/90_SOCIALMEDIA.html @@ -2,7 +2,7 @@

    On social media