From 031282dcbff13f79a791577e847074cb8e3951ef Mon Sep 17 00:00:00 2001 From: Robert Soulliere Date: Thu, 16 Sep 2010 08:41:54 -0400 Subject: [PATCH] Clean up a few more admin files. --- 1.6/admin/AdminMisc.xml | 5 +- 1.6/admin/Upgrading-Evergreen_1.6.xml | 42 ++++---- 1.6/admin/admin-lsa.xml | 2 +- 1.6/admin/serveradministration.xml | 148 +++++++++++++------------- 1.6/admin/troubleshooting.xml | 8 +- 5 files changed, 102 insertions(+), 103 deletions(-) diff --git a/1.6/admin/AdminMisc.xml b/1.6/admin/AdminMisc.xml index 33f6f6e264..cb66410b72 100644 --- a/1.6/admin/AdminMisc.xml +++ b/1.6/admin/AdminMisc.xml @@ -51,7 +51,7 @@ web serverApache for the OPAC to work correctly. To stop Evergreen, run: osrf_ctl.sh -l -a stop_all - As with starting, you can choose to stop one service + As with starting, you can choose to stop services individually. To restart Evergreen, run: osrf_ctl.sh -l -a restart_all @@ -67,8 +67,7 @@ PostgreSQL database. You can therefore use normal PostgreSQL backup procedures to backup this data. For example, the simplest method of backing up the Evergreen database is to use the pg_dump command to create a live backup of the database without having to - interrupt any Evergreen services: - # pg_dump -U [username] -h [hostname] -f [output-file] [database-name] + interrupt any Evergreen services. Here is an example pg_dump command which will dump a local Evergreen database into a the file evergreen_db.backup: pg_dump -U evergreen -h localhost -f evergreen_db.backup evergreen To restore the backed up database into a new database, create a new database using the template0 database template and the UTF8 encoding, and run the psql command, specifying the new diff --git a/1.6/admin/Upgrading-Evergreen_1.6.xml b/1.6/admin/Upgrading-Evergreen_1.6.xml index 1ef37957e5..a194b373f1 100644 --- a/1.6/admin/Upgrading-Evergreen_1.6.xml +++ b/1.6/admin/Upgrading-Evergreen_1.6.xml @@ -114,16 +114,16 @@ /openils/bin/srfsh srfsh# request opensrf.math add 2 2 You should see output like: - - Received Data: 4 - - ------------------------------------ - Request Completed Successfully - Request Time in seconds: 0.007519 - ------------------------------------ - - srfsh# - + +Received Data: 4 + +------------------------------------ +Request Completed Successfully +Request Time in seconds: 0.007519 +------------------------------------ + +srfsh# + If test completed successfully move onto next section. Otherwise, refer to the troubleshooting chapter of this documentation. @@ -198,12 +198,12 @@ As the root user, build live-db-setup.pl for the cgi-bin bootstrapping scripts and offline-config.pl for the offline staff client data uploader: cd /home/opensrf/Evergreen-ILS-1.6.0.8 - - - perl Open-ILS/src/support-scripts/eg_db_config.pl --create-bootstrap --create-offline --user evergreen \ - --password evergreen --hostname localhost --port 5432 --database evergreen - - + + +perl Open-ILS/src/support-scripts/eg_db_config.pl --create-bootstrap --create-offline --user evergreen \ +--password evergreen --hostname localhost --port 5432 --database evergreen + + As the opensrf user, update server symlink in /openils/var/web/xul/: @@ -249,11 +249,11 @@ psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/1.6.0.7-1.6.0.8-upgrade-db Update opensrf.xml with the database connection info: - - - perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config --service all --user evergreen \ - --password evergreen --hostname localhost --port 5432 --database evergreen - + + +perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config --service all --user evergreen \ +--password evergreen --hostname localhost --port 5432 --database evergreen + diff --git a/1.6/admin/admin-lsa.xml b/1.6/admin/admin-lsa.xml index 6e8ee6f671..d3eb019b65 100644 --- a/1.6/admin/admin-lsa.xml +++ b/1.6/admin/admin-lsa.xml @@ -39,7 +39,7 @@ Items on this menu are visible to anyone logged into the staff client but usually require special permissions to edit. The following table describes each of the menu options. - + diff --git a/1.6/admin/serveradministration.xml b/1.6/admin/serveradministration.xml index c58e323d53..ea4af21f96 100644 --- a/1.6/admin/serveradministration.xml +++ b/1.6/admin/serveradministration.xml @@ -1716,54 +1716,54 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Create a marc template in the directory /openils/var/templates/marc/. It should be in xml format. Here is an example file k_book.xml: - - - 00620cam a2200205Ka 4500 - 070101s eng d - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ]]> - + + + 00620cam a2200205Ka 4500 + 070101s eng d + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +]]> + @@ -1772,7 +1772,7 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Restart PerlPerl services for changes to take effect. - /openils/bin/osrf_ctl.sh -l -a restart_perl + /openils/bin/osrf_ctl.sh -l -a restart_perl @@ -2011,47 +2011,47 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="serveradministrati Clone the title|proper index to create a keyword|title index 6 = the title|proper index - - INSERT INTO config.metabib_field - (field_class, name, xpath, weight, format, search_field, facet_field) - SELECT 'keyword', 'title', xpath, weight, format, search_field, facet_field - FROM config.metabib_field - WHERE id = 6; - + +INSERT INTO config.metabib_field + (field_class, name, xpath, weight, format, search_field, facet_field) + SELECT 'keyword', 'title', xpath, weight, format, search_field, facet_field + FROM config.metabib_field + WHERE id = 6; + Populate the keyword|title index with a set of index entries cloned from the metabib.title_field_entry table; 6 = the title|proper index - - INSERT INTO metabib.keyword_field_entry - (source, field, value) - SELECT source, 17, value (the field value, 17, field be different in your database so you may need to check the - config.metabib_field for the id of your new index). - FROM metabib.title_field_entry - WHERE field = 6; - + +INSERT INTO metabib.keyword_field_entry + (source, field, value) + SELECT source, 17, value (the field value, 17, field be different in your database so you may need to check the + config.metabib_field for the id of your new index). + FROM metabib.title_field_entry + WHERE field = 6; + Bump the relevance when the first search term appears first in the title in a keyword search. 17 = our new keyword|title index (This may be different in your database so you may need to check the config.metabib_field for the id of your new index). - - INSERT INTO search.relevance_adjustment - (active, field, bump_type, multiplier) - VALUES (true, 17, 'first_word', 5); - + +INSERT INTO search.relevance_adjustment + (active, field, bump_type, multiplier) +VALUES (true, 17, 'first_word', 5); + Boost the relevance for search terms appearing in the title in general 17 = our new keyword|title index (This may be different in your database so you may need to check the config.metabib_field for the id of your new index). - - UPDATE config.metabib_field - SET weight = 10 - WHERE id = 17; - + +UPDATE config.metabib_field +SET weight = 10 +WHERE id = 17; + diff --git a/1.6/admin/troubleshooting.xml b/1.6/admin/troubleshooting.xml index 99b46c617b..b354d99059 100644 --- a/1.6/admin/troubleshooting.xml +++ b/1.6/admin/troubleshooting.xml @@ -184,10 +184,10 @@ srfsh# or apache2ctl start You should see output: - - * Starting web server apache2 - ...done. - + +* Starting web server apache2 +...done. + the Apache OpenSRF modules write to the /openils/var/log/gateway.loglogsgateway.log However, you should check all of the log files for errors: -- 2.43.2