Add missing option to the eg config script command reported in bug report https:...

diff --git a/2.0/admin/serversideinstallation_2.0.xml b/2.0/admin/serversideinstallation_2.0.xml
index 89a6f5f..a2f3759 100644 (file)
--- a/2.0/admin/serversideinstallation_2.0.xml
+++ b/2.0/admin/serversideinstallation_2.0.xml
@@ -1050,14 +1050,16 @@
        perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config \\r
          --service all --create-schema --create-offline \\r
          --hostname HOSTNAME --port PORT \\r
-         --user evergreen --password PASSWORD --database DATABASENAME</userinput>\r
+         --user evergreen --password PASSWORD --database DATABASENAME --admin-user ADMIN-USER --admin-pass ADMIN-PASSWORD </userinput>\r
                                                        </screen>\r
                                                        <para>On most systems, <emphasis>HOSTNAME</emphasis> will be\r
                                                        <emphasis role="bold">localhost</emphasis> and\r
                                                        <emphasis>PORT</emphasis> will be <emphasis role="bold">5432</emphasis>.\r
                                                        Of course, values for <emphasis>PASSWORD</emphasis> and\r
                                                        <emphasis>DATABASENAME</emphasis> must match the values you used in \r
-                                                       <xref linkend="serversideinstallation-postgresqlcreateuser"/>.</para>\r
+                                                       <xref linkend="serversideinstallation-postgresqlcreateuser"/>. The <option>admin-user</option> and <option>admin-pass</option> options will \r
+                                                       specify the Evergreen administrator account's username and password. This was \r
+                                                       changed for security reasons, it was previously admin/open-ils</para>\r
                                                        <para>As the command executes, you may see warnings similar to:\r
                                                        <literal>ERROR: schema SOMENAME does not exist</literal> (in fact,\r
                                                        you may see one warning per schema) but they can be safely ignored.</para>\r
@@ -1182,11 +1184,10 @@
                                                                        applications on your server:</para>\r
                                                                        \r
                                                                        <para>Edit the Apache configuration file and change the lines:</para>\r
-                                                                       <screen>\r
-                                                                               <userinput>\r
-       export APACHE_RUN_USER=www-data\r
-       export APACHE_RUN_GROUP=www-data</userinput>\r
-                                                                       </screen>\r
+<screen>\r
+<userinput>export APACHE_RUN_USER=www-data</userinput>\r
+<userinput>export APACHE_RUN_GROUP=www-data</userinput>\r
+</screen>\r
                                                                        <para>to instead read:</para>\r
                                                                        <screen>\r
                                                                                <userinput>\r