/dev/random has created the same effect as /dev/arandom (and /dev/urandom)

for quite some time.  Mop up the last few, by using /dev/random where we
actually want it, or not even mentioning arandom where it is irrelevant.

1 files changed, 3 insertions, 3 deletions

diff --git a/libexec/spamd/spamd.8 b/libexec/spamd/spamd.8
index cfca6aed33e..9ff89f64e09 100644
--- a/libexec/spamd/spamd.8
+++ b/libexec/spamd/spamd.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: spamd.8,v 1.122 2014/10/11 20:06:31 landry Exp $
+.\"	$OpenBSD: spamd.8,v 1.123 2014/11/22 18:15:41 deraadt Exp $
 .\"
 .\" Copyright (c) 2002 Theo de Raadt.  All rights reserved.
 .\"
@@ -22,7 +22,7 @@
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: October 11 2014 $
+.Dd $Mdocdate: November 22 2014 $
 .Dt SPAMD 8
 .Os
 .Sh NAME
@@ -573,7 +573,7 @@ and use it as a shared key to authenticate the synchronisation messages.
 The file itself can contain any data.
 For example, to create a secure random key:
 .Bd -literal -offset indent
-# dd if=/dev/arandom of=/etc/mail/spamd.key bs=2048 count=1
+# dd if=/dev/random of=/etc/mail/spamd.key bs=2048 count=1
 .Ed
 .Pp
 The file needs to be copied to all hosts