From da9d87dbaed4893cc2fcf364f73b8a3da99875ba Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Sun, 4 Oct 2020 17:48:50 +0000 Subject: doc: fix URLs --- doc/s6-fillurandompool.html | 6 +++--- doc/s6-ps.html | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/s6-fillurandompool.html b/doc/s6-fillurandompool.html index 9be985e..c07b0f4 100644 --- a/doc/s6-fillurandompool.html +++ b/doc/s6-fillurandompool.html @@ -40,13 +40,13 @@ Reading from /dev/random blocks when its entropy pool is not full enough, so it will never return weak random data. (Reading from /dev/random is overkill anyway, and -you +you should not be doing it.)

However, reading from /dev/urandom (which -you should be doing) +you should be doing) will not block, even though the entropy pool may not have been initialized yet. That's the only insecure thing about it: at boot time, /dev/urandom may return weak random data, until its entropy @@ -66,7 +66,7 @@ random data, until the machine shuts down.

diff --git a/doc/s6-ps.html b/doc/s6-ps.html index 5e1887f..12a986c 100644 --- a/doc/s6-ps.html +++ b/doc/s6-ps.html @@ -117,7 +117,7 @@ usage.
  • cttime : total CPU time used by the process and all its dead children (user + kernel mode).
  • tstart : the start time of the process as a -TAI64N value.
  • +TAI64N value.
  • cpcpu : the percentage of CPU used by the process and its dead children (total cpu time divided by total running time). It is a mean value and does not reflect current CPU -- cgit 1.4.1