typo fixed from pamela@ thanks!

This commit is contained in:
Solene Rapenne 2021-10-10 20:43:14 +02:00
parent 7ce232489e
commit a337a52277
4 changed files with 5 additions and 5 deletions

View File

@ -3,6 +3,6 @@
<ul>
<li>OpenBSD 7.0 released!</li>
<li>No more packages updates for 6.9, syspatch will still be published</li>
<li>No more syspatches for 6.8, it is now end of life and shouldn't be used anymore</li>
<li>No more syspatches for 6.8, it is now end of life and shouldn't be used any longer</li>
</ul>
</article>

View File

@ -9,7 +9,7 @@
<li>xterm has unveil</li>
<li>base gcc removed on amd64</li>
<li>bsd-reconfig to have a KARL compatible modified kernel</li>
<li>new <em>dhcpleased</em> and <em>resolvd</em> superseeding dhclient (now default for new installs). After upgrade you can switch to it: replace <code>dhcp</code> by <code>autoconf</code> in your network <code>hostname.if</code> file then enable and start the two services</li>
<li>new <em>dhcpleased</em> and <em>resolvd</em> superseding dhclient (now default for new installs). After upgrade you can switch to it: replace <code>dhcp</code> by <code>autoconf</code> in your network <code>hostname.if</code> file then enable and start the two services</li>
<li>performance improvements for heavy loads on many cores</li>
<li><a href="https://www.openbsd.org/plus70.html" class="permalink">Many other changes!</a></li>
</ul>

View File

@ -3,6 +3,6 @@
<h2>Shell tips</h2>
<p>OpenBSD 7.0 comes with a new utility named <em>timeout</em> to run a command and stop it after an user defined time. The <a class="permalink" href="https://man.openbsd.org/timeout">man page</a> 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, <em>timeout</em> 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 <code>timeout 8h rsync -a /data/ remote:/data/</code> and started from a cron job at 00h00. In this case rsync would run at midnight and <em>timeout</em> 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 <code>timeout 8h rsync -a /data/ remote:/data/</code> and started from a cron job at 00h00. In this case rsync would run at midnight and <em>timeout</em> would stop it at 8h00 if the job is not finished.
</p>
</article>

View File

@ -2,7 +2,7 @@
<div class="puffies" aria-hidden="true">🐡🐡🐡</div>
<h2>On social media</h2>
<ul>
<li><a class="permalink" href="https://news.ycombinator.com/item?id=28711519">We did hit first page of hackernews at launch</a></li>
<li><a class="permalink" href="https://bsd.network/@bcallah/107037881574770525">thfr@ needing help for improving audio support in the video game Celeste</a></li>
<li><a class="permalink" href="https://news.ycombinator.com/item?id=28711519">We hit the first page of hackernews at launch</a></li>
<li><a class="permalink" href="https://bsd.network/@bcallah/107037881574770525">thfr@ needs help for improving audio support in the video game Celeste</a></li>
</ul>
</article>