random.4: Rework formatting of /proc interfaces

Make the information easier to parse by formatting the file
descriptions as hanging lists. No significant content changes.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-11-10 13:31:59 +01:00
parent af0b099051
commit 388ee0f4b6
1 changed files with 18 additions and 18 deletions

View File

@ -221,25 +221,25 @@ run during the Linux system shutdown:
In the above examples, we assume Linux 2.6.0 or later, where
.IR /proc/sys/kernel/random/poolsize
returns the size of the entropy pool in bits (see below).
.SS /proc Interface
.\"
.SS /proc interfaces
The files in the directory
.I /proc/sys/kernel/random
(present since 2.3.16) provide an additional interface to the
(present since 2.3.16) provide additional information about the
.I /dev/random
device.
.LP
The read-only file
device:
.TP
.I entropy_avail
gives the available entropy.
This read-only file gives the available entropy.
Normally, this will be 4096 (bits),
a full entropy pool.
.LP
The file
.TP
.I poolsize
This file
gives the size of the entropy pool.
The semantics of this file vary across kernel versions:
.RS
.TP 12
.TP
Linux 2.4:
This file gives the size of the entropy pool in
.IR bytes .
@ -247,20 +247,21 @@ Normally, this file will have the value 512, but it is writable,
and can be changed to any value for which an algorithm is available.
The choices are 32, 64, 128, 256, 512, 1024, or 2048.
.TP
Linux 2.6:
Linux 2.6 and later
This file is read-only, and gives the size of the entropy pool in
.IR bits .
It contains the value 4096.
.RE
.LP
The file
.TP
.I read_wakeup_threshold
This file
contains the number of bits of entropy required for waking up processes
that sleep waiting for entropy from
.IR /dev/random .
The default is 64.
The file
.TP
.I write_wakeup_threshold
This file
contains the number of bits of entropy below which we wake up
processes that do a
.BR select (2)
@ -269,14 +270,13 @@ or
for write access to
.IR /dev/random .
These values can be changed by writing to the files.
.LP
The read-only files
.I uuid
and
.I boot_id
.TP
.IR uuid " and " boot_id
These read-only files
contain random strings like 6fd5a44b-35f4-4ad4-a9b9-6b9be13e1fe9.
The former is generated afresh for each read, the latter was
generated once.
.\"
.SS ioctl(2) interface
The following
.BR ioctl (2)