From 87070ccc137120e1ecb0493dad68b508fd9c43d7 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 24 Jan 2001 15:19:36 +0000
Subject: [PATCH] It looks Ok, but it has one unnecessary step. There is no
 need to do the "mv privkey.pem cert.pem.pw" if you just use "privkey.pem" in
 the following openssl command (e.g. openssl rsa -in privkey.pem -out
 cert.pem". But there is nothing wrong with it as it is now, as far as I can
 see.

//Magnus
---
 doc/src/sgml/runtime.sgml | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 81d0846e00..17dcc10f84 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.46 2001/01/08 21:01:54 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.47 2001/01/24 15:19:36 momjian Exp $
 -->
 
 <Chapter Id="runtime">
@@ -1911,8 +1911,7 @@ openssl req -new -text -out cert.req
    To remove the passphrase (as you must if you want automatic start-up of
    the postmaster), run the commands
 <programlisting>
-mv privkey.pem cert.pem.pw
-openssl rsa -in cert.pem.pw -out cert.pem 
+openssl rsa -in privkey.pem -out cert.pem
 </programlisting>
    Enter the old passphrase to unlock the existing key. Now do
 <programlisting>