From bd5d7cc50db31904217a1ce14c33524f0c261af1 Mon Sep 17 00:00:00 2001 From: Steve Sheppard Date: Sun, 29 Aug 2010 18:38:56 -0400 Subject: [PATCH] rewrite NOTE and WARNING messages; add [[ COMMENTS ]] where appropriate; add new "Post-Installation Chores" section; --- 1.6/admin/ServersideInstallation.xml | 291 +++++++++++++++++---------- 1 file changed, 184 insertions(+), 107 deletions(-) diff --git a/1.6/admin/ServersideInstallation.xml b/1.6/admin/ServersideInstallation.xml index ae56b65dc5..2517428e48 100644 --- a/1.6/admin/ServersideInstallation.xml +++ b/1.6/admin/ServersideInstallation.xml @@ -16,7 +16,7 @@ System Requirements This section describes various requirements of the hardware and software environment that must be fulfilled to support a successful Evergreen installation. For a description of the installation process itself and for links to further instructions please review the section "The Installation Process" . The system requirements for running Evergreen really depend on what you want to do with it. For just evaluating the software, or for a very small library (for example, 1 circulation station, a few thousand items, and infrequent online catalog use), any modern desktop or laptop made within the last few years capable of running Linux, FreeBSD, etc. should suffice. We recommend at least 512mb of RAM. - [[ Other hardware and software requirements ]] + [[ ADD OTHER HARDWARE AND SOFTWARE REQUIREMENTS ]] From Dan Scott on [http://list.georgialibraries.org/pipermail/ @@ -85,15 +85,15 @@
PINES In order to provide load balancing and high-availability at the OPAC and Staff Client level, PINES has implemented a Linux Virtual Server environment with five independent mini-clusters. This allows live updates of the entire system with no perceived downtime or interruption in service. - [[ further information on PINES ]] + [[ ADD FURTHER INFORMATION ON PINES ]]
Sitka - [[ further information on Sitka ]] + [[ ADD FURTHER INFORMATION ON SITKA ]]
Other working systems - [[ further information on other working systems ]] + [[ ADD FURTHER INFORMATION ON OTHER WORKING SYSTEMS ]]
@@ -101,38 +101,41 @@ Installing, configuring and testing the Evergreen server-side software is straightforward with the current stable software release. Earlier software distributions are also available. In the following sections you will find instructions tailored to specific distributions.
Current Stable Software Release - The current stable release of Evergreen is version 1.6.0.7. Instructions for installing, configuring and testing that version on the Ubuntu or Debian Linux systems are found in the section "Installing Evergreen 1.6.0.7 on Ubuntu or Debian" . + The current stable release of Evergreen is version 1.6.0.7. Instructions for installing, configuring and testing that version on the Ubuntu or Debian Linux systems are found in the section "Installing Evergreen on Ubuntu or Debian" . - This release of Evergreen software is dependent on the OpenSRF software system. The current stable release of OpenSRF is version 1.0.6. Instructions for installing, configuring and testing that version are found in the section "Installing OpenSRF" . + This release of Evergreen software is dependent on the Open Service Request Framework (OpenSRF) software framework. The current stable release of OpenSRF is version 1.2.2. Instructions for installing, configuring and testing that version are found in the section "Installing OpenSRF" .
Previous Software Releases Earlier releases of Evergreen are also available. Instructions for installing, configuring and testing earlier versions are found in the section Installing Previous Versions of Evergreen . - The most recent previous release of Evergreen is version 1.4.0.6. Instructions for installing, configuring and testing that version are found in the section Installing Evergreen 1.4.0.6 on Ubuntu or Debian . + The next most recent previous release of Evergreen is version 1.4.0.6. Instructions for installing, configuring and testing that version are found in the section Installing Evergreen 1.4.0.6 on Ubuntu or Debian . - The most recent previous release of OpenSRF is version 1.0.x. Instructions for installing, configuring and testing that version are found in the section Installing OpenSRF 1.0.x . + The accompanying previous release of OpenSRF is version 1.0.x. Instructions for installing, configuring and testing that version are found in the section Installing OpenSRF 1.0.x .
- Installing Evergreen 1.6.0.7 On Ubuntu or Debian + Installing Evergreen On Ubuntu or Debian + This section outlines the installation process for the latest stable version of Evergreen (1.6.0.7). + The following steps have been tested on the x86 (32-bit) and x86-64 (64-bit) architectures. There may be differences between the Desktop and Server editions of Ubuntu. These instructions assume the Server edition. In the following instructions, you are asked to perform certain steps as either the root user, the opensrf user, or the postgres user. To become the root user, issue the command: su - root. To switch from the root user to a different user, issue a command like: su - USERNAME. For example, to switch from the root user to the opensrf user, issue this command: su - opensrf. Once you have become a non-root user, to become the root user again, simply issue the exit command. -
- Installing the latest version of OpenSRF - For further information on installing the Open Service Request Framework (OpenSRF), see the section "Installing OpenSRF" . - Follow the steps outlined in that section, then run the specified test(s) to ensure that OpenSRF is properly installed before continuing with any further Evergreen installation steps. The Evergreen application depends on properly installation of OpenSRF. If OpenSRF does not work correctly, Evergreen will not work properly either. -
Downloading and Building Evergreen - In this section, you will download, unpack, install, configure and test the Evergreen system, including the Evergreen server and the PostgreSQL database system. You will make several configuration changes and adjustments to the software, including updates to configure the system for your own locale, and some updates needed to work around a few known issues. + In this section you will download, unpack, install, configure and test the Evergreen system, including the Evergreen server and the PostgreSQL database system. You will make several configuration changes and adjustments to the software, including updates to configure the system for your own locale, and some updates needed to work around a few known issues. As far as possible, perform the following steps in the order they are given, since the success of many steps relies on the successful completion of earlier steps. You should make backup copies of files and environments when you are instructed to do so. In the event of installation problems those copies can allow you to back out of a step gracefully and resume the installation from a known state. Of course, after you successfully complete and test the entire Evergreen installation you should take a final snapshot backup of your system(s). This can be the first in the series of regularly scheduled system backups that you should probably also begin. +
+ Installing OpenSRF + Evergreen software is integrated with and depends on the Open Service Request Framework (OpenSRF) software system. For further information on installing, configuring and testing OpenSRF, see the section "Installing OpenSRF" . + Follow the steps outlined in that section and run the specified tests to ensure that OpenSRF is properly installed and configured. Do not continue with any further Evergreen installation steps until you have verified that OpenSRF has been successfully installed. +
Download and Unpack Latest Evergreen Version As the opensrf user, download and extract the latest version of Evergreen. The latest version can be found here: + [[ VERIFY LOCATION OF LATEST VERSION OF EVERGREEN ]]
Commands to download/extract Evergreen @@ -144,15 +147,22 @@
Install Prerequisites to Build Evergreen - In this step you will install and configure a set of prerequisites for building Evergreen. In a following step you will actually build the software. - As the root user, build the prerequisites from the software distribution that you just downloaded and unpacked. Enter the commands show below. Remember to replace [distribution] in the following example with the keyword that corresponds to your actual Linux distribution (see the following list): + In this step you will install and configure a set of prerequisites used to build the Evergreen server-side software. In a following step you will actually build the software. + As the root user, enter the commands show below to build the prerequisites from the software distribution that you just downloaded and unpacked. Remember to replace [distribution] in the following example with the keyword that corresponds to the actual Linux distribution listed here: + debian-lenny for Debian Lenny (5.0), the most recent version debian-etch for Debian Etch (4.0) - debian-lenny for Debian Lenny (5.0) - [[other Debian distributions]] + + ubuntu-karmic for Ubuntu Lucid (10.04) [same as for Karmic] + ubuntu-karmic for Ubuntu Karmic (9.10) + ubuntu-intrepid for Ubuntu Intrepid (8.10) ubuntu-hardy for Ubuntu Hardy (8.04) - ubuntu-karmic for Ubuntu Karmic (9.10) and Ubuntu Lucid (10.04) - [[other Ubuntu distributions]] + ubuntu-gutsy for Ubuntu Gutsy (7.10) + + gentoo generic for Gentoo versions + centos generic for Centos versions + + [[ ADD INFO FOR OTHER LINUX DISTRIBUTIONS ]]
Commands to install prerequisites for Evergreen @@ -180,9 +190,13 @@ $ make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_84
- Note: PostgreSQL 8.1 is deprecated and will become unsupported in a future release, though existing installations upgrading from Evergreen 1.4 or before will work fine. However, consider upgrading your Postgres soon! - [[ is this still true? ]] - [[ how to determine which version of PostgreSQL you have? ]] + + + PostgreSQL 8.1 is deprecated and will become unsupported in a future release, though existing installations upgrading from Evergreen 1.4 or before will work fine. However, consider upgrading your Postgres soon! + + + [[ VERIFY: IS THIS STILL TRUE? ]] + [[ ADD INFO ON HOW TO DETERMINE WHICH VERSION OF POSTGRESQL YOU HAVE ]]
(OPTIONAL) Install Perl Modules on PostgreSQL Server @@ -202,8 +216,8 @@ cpan> install MARC::File::XML - [[ how to install the Perl modules ]] - [[ how to verify that the Perl modules are installed ]] + [[ ADD INFO ON HOW TO INSTALL THE PERL MODULES ]] + [[ ADD INFO ON HOW TO VERIFY THAT THE PERL MODULES ARE INSTALLED ]]
Add Additional Library Paths on Evergreen System @@ -223,7 +237,7 @@
(OPTIONAL) Restart the PostgreSQL Service If PostgreSQL is running on the same system as the rest of Evergreen, as the root user you must restart the PostgreSQL service to avoid a problem where the library plperl.so cannot be found. If your PostgreSQL server is running on another system, just skip this step. - [[ other versions of PostgreSQL ]] + [[ ADD INFO ON OTHER VERSIONS OF POSTGRESQL ]]
Commands to restart PostgreSQL service @@ -332,12 +346,14 @@ --user [USER] --password [PASSWORD] --database [DATABASENAME]
- - NOTE: If you are entering the above command on a single line, do not include the ''\'' characters. If you are using the bash shell, these should only be used at the end of a line at a bash prompt to indicate that the command is continued on the next line. - + + + If you are entering the above command on a single line, do not include the \ (backslash) characters. If you are using the bash shell, these should only be used at the end of a line at a bash prompt to indicate that the command is continued on the next line. + +
- Setup the Apache Server + Configure the Apache Server As the root user, configure the Apache server and copy several new configuration files to the Apache server directories:
Commands to configure the Apache server @@ -367,104 +383,131 @@ $ openssl req -new -x509 -days 365 -nodes -out server.crt -keyout server.key
- Warning: This is only a temporary measure to expedite testing. You must get a proper SSL certificate for a public production system. See this section for further comments on setting up a properly signed SSL certificate: - [[how to get a signed SSL certificate]] + + + This is only a temporary measure to expedite testing. You must get a proper SSL certificate for a public production system. See this section for further comments on setting up a properly signed SSL certificate: + + + [[ ADD INFO ON HOW TO GET A SIGNED SSL CERTIFICATE ]]
Modify the Apache Configuration File - Edit the Apache configuration file /etc/apache2/sites-available/eg.conf and make the following changes: + As the root user, edit the Apache configuration file /etc/apache2/sites-available/eg.conf and make the following changes: - Comment out the line Allow from 10.0.0.0/8, then uncomment the line Allow from all. This is a temporary measure to expedite testing. + Comment out the line Allow from 10.0.0.0/8, then uncomment the line Allow from all. - Warning: You must remove these changes after testing is completed. This will enable access to the configuration CGI scripts from any workstation on any network. You must secure this for a public production system, preferably by explicitly specifying the allowed IP addresses and adding proper authentication. + This change allows access to your configuration CGI scripts from any workstation on any network. It is a temporary change to expedite testing and should be removed after you have finished and successfully tested the Evergreen installation. + + + You must remove these changes after testing is completed. See the section "Post-Installation Chores" for further details on removing this change after the Evergreen installation is complete. + + - Comment out the line Listen 443 as it conflicts with the same declaration in the configuration file: /etc/apache2/ports.conf . - [[Debian Etch users - do not do this!]] + Comment out the line Listen 443 as it conflicts with the same declaration in the configuration file: /etc/apache2/ports.conf . Debian etch users should not do this. + [[ ADD INFO ON WHY DEBIAN ETCH USERS SHOULD NOT DO THIS ]] - -
-
- Modifications to Keep the Logs Functioning - You must modify the Apache configuration file to allow the logs to function properly, but it may break other Apache applications on your server. We hope to make this unnecessary soon. - [[ is this still necessary ? ]] - - For the Linux distributions Ubuntu Hardy / Debian Etch , as the root user, edit the Apache configuration file /etc/apache2/apache2.conf and change the user: - www-data - to the user: - opensrf + The following updates are needed to allow the logs to function properly, but it may break other Apache applications on your server. We hope to make this unnecessary soon. + [[ ADD INFO ON WHETHER THIS IS STILL NECESSARY ]] + + + For the Linux distributions Ubuntu Hardy or Debian Etch, as the root user, edit the Apache configuration file /etc/apache2/apache2.conf and change the user: + www-data + to the user: + opensrf + + + For the Linux distributions Ubuntu Karmic or Ubuntu Lucid or Debian Lenny, as the root user, edit the Apache configuration file /etc/apache2/envvars and change the phrase: + export APACHE_RUN_USER=www-data + to the phrase: + export APACHE_RUN_USER=opensrf + + - For the Linux distributions Ubuntu Karmic / Ubuntu Lucid / Debian Lenny , as the root user, edit the Apache configuration file /etc/apache2/envvars and change the phrase: - export APACHE_RUN_USER=www-data - to the phrase: - export APACHE_RUN_USER=opensrf + As the root user, edit the Apache configuration file /etc/apache2/apache2.conf and add the line KeepAliveTimeout 1, or modify an existing line if it already exists. - -
-
- Modify Apache Configuration File - As the root user, edit the Apache configuration file /etc/apache2/apache2.conf and add the line KeepAliveTimeout 1, or modify an existing line if it already exists. +
(OPTIONAL) Performance Modifications for Apache - As the root user, edit the Apache configuration file /etc/apache2/apache2.conf and add the line MaxKeepAliveRequests 100, or modify an existing line if it already exists. Additionally, locate and modify the section related to prefork configuration to suit the load on your system. - Following are settings that may apply to a busy system: -
- "Prefork configuration" section of Apache configuration file - - <IfModule mpm_prefork_module> - StartServers 20 - MinSpareServers 5 - MaxSpareServers 15 - MaxClients 150 - MaxRequestsPerChild 10000 - </IfModule> - -
- [[ settings of "prefork configuration" section for busy/notbusy systems ]] + Some further configuration changes to Apache may be necessary for busy systems. These changes increase the number of Apache server processes that can be started to support additional browser connections, and are made to the prefork configuration section of the Apache configuration file. + + As the root user, edit the Apache configuration file /etc/apache2/apache2.conf and add the line MaxKeepAliveRequests 100, or modify an existing line if it already exists. + + As the root user, edit the Apache configuration file /etc/apache2/apache2.conf, locate and modify the section related to prefork configuration to suit the load on your system. +
+ (OPTIONAL) Updates to Apache configuration + + <IfModule mpm_prefork_module> + StartServers 20 + MinSpareServers 5 + MaxSpareServers 15 + MaxClients 150 + MaxRequestsPerChild 10000 + </IfModule> + + MaxKeepAliveRequests 100 + +
+ +
Enable the Evergreen Site - As the root user, enable the Evergreen site: + You must run additional Apache configuration commands to enable the Evergreen web site. As the root user, run these commands:
- Commands to enabl e the Evergreen site + Apache Commands to Enable the Evergreen Web Site $ su - root - $ a2dissite default # OPTIONAL: disable the default site (i.e., the "It Works" page). + + # disables the default site (i.e., the "It Works" page). + $ a2dissite default + + # enables the Evergreen web site $ a2ensite eg.conf
Modify the OpenSRF Configuration File - As the opensrf user, edit the OpenSRF configuration file /openils/conf/opensrf_core.xml to update the Jabber usernames and passwords, and to specify the domains from which we'll accept and to which we'll make connections. - If you are installing Evergreen on a single server and using the ~private.localhost~ / ~public.localhost~ domains, these will already be set to the correct values. Otherwise, search and replace to match your customized values. - Note: the following example uses common XPath syntax on the left-hand side to indicate the position within the XML file: + As the opensrf user, edit the OpenSRF configuration file /openils/conf/opensrf_core.xml to update various usernames and passwords, and to specify the domains from which we will accept and to which we will make connections. + If you are installing Evergreen on a single server and using the private.localhost / public.localhost domains, these will already be set to the correct values. Otherwise, search and replace to match your customized values. + + + The following example uses common XPath syntax on the left-hand side to indicate the aproximage position needing changes within the XML file. + + + [[ ADD A BETTER DIAGRAM HERE ]]
- Updates needed to the file /openils/conf/opensrf_core.xml + Updates needed to the file "/openils/conf/opensrf_core.xml" /config/opensrf/username = opensrf - /config/opensrf/passwd = password for **private.localhost** opensrf user + + /config/opensrf/passwd = password for "private.localhost" opensrf user + /config/gateway/username = opensrf - /config/gateway/passwd = password for **public.localhost** opensrf user - /config/routers/router/transport - first entry, where ''transport/server'' == **public.localhost** : + + /config/gateway/passwd = password for "public.localhost" opensrf user + + # first entry, where "transport/server" == "public.localhost" : + /config/routers/router/transport username = router - password = password for **public.localhost** router user - /config/routers/router/transport'' - second entry, where ''transport/server'' == **private.localhost** : + password = password for "public.localhost" router user + # second entry, where "transport/server" == "private.localhost" : + /config/routers/router/transport username = router - password = password for **private.localhost** router user + password = password for "private.localhost" router user
- [[ better diagram needed here ]]
- Create Private Configuration Files for Certain Users - The software installation will automatically create a utility named srfsh (surf shell). This is a command line diagnostic tool for interacting with the OpenSRF network software. You must set up a special configuration file for each user who will need to run the utility. - Copy the file /openils/conf/srfsh.xml.example to the file .srfsh.xml in the home directory of each user who will use srfsh. Finally, edit each file .srfsh.xml and make the following changes: + Create Configuration Files for Users Needing srfsh + The software installation will automatically create a utility named srfsh (surf shell). This is a command line diagnostic tool for testing and interacting with the OpenSRF network software. It will be used in a future step to complete and test the Evergreen installation. See the section "Testing the Installation" for further information. + In this step you will set up a special configuration file for each user who will need to run the utility. Copy the short sample configuration file /openils/conf/srfsh.xml.example to the file .srfsh.xml (note the leading dot!) in the home directory of each user who will use srfsh. Finally, edit each file .srfsh.xml and make the following changes: Modify domain to be the router hostname (following our domain examples, private.localhost will give the utility srfsh access to all OpenSRF services, while public.localhost will only allow access to those OpenSRF services that are publicly exposed). Modify username and password to match the opensrf Jabber user for the chosen domain @@ -492,8 +535,12 @@
Modify the OpenSRF Environment - As the opensrf user, change the file permissions the directory /openils/var/cgi-bin to executable, then modify the shell configuration file ~/.bashrc of that user by adding a Perl environmental variable. - Note: in a multi-server environment, you must add the modifications to ~/.bashrc at the top of the file before the line [ -z "$PS1" ] && return. This will allow headless (scripted) logins to load the correct environment. + As the opensrf user, change the file permissions of the directory /openils/var/cgi-bin to executable, then modify the shell configuration file ~/.bashrc of that user by adding a Perl environmental variable. Finally, execute the shell configuration file to load the new variables into your current environment. + + + In a multi-server environment, you must add any modifications to ~/.bashrc to the top of the file before the line [ -z "$PS1" ] && return. This will allow headless (scripted) logins to load the correct environment. + +
Modify the OpenSRF environment @@ -503,13 +550,16 @@ # add environmental variable $ echo "export PERL5LIB=/openils/lib/perl5:\$PERL5LIB" >> ~/.bashrc - $ . ~/.bashrc # inherit the new environment + + # inherit the new environment + $ . ~/.bashrc
-
+
(OPTIONAL) Configuration for Other Languages - Load translations such as Armenian (hy-AM), Canadian French (fr-CA), and others into the database to complete the translations available in the OPAC and Staff Client. See the section "Adding Language Localization" for details. + This section describes how translations such as Armenian (hy-AM), Canadian French (fr-CA) and others are loaded into the database to complete the translations (default English) available in the OPAC and Staff Client. + [[ ADD SECTION ON LANGUAGE LOCALIZATION ]]
@@ -542,8 +592,12 @@ $ osrf_ctl.sh -l -a start_all - Note: You can also start Evergreen without the -l flag, but the utility osrf_ctl.sh must know the fully qualified domain name for the system on which it will execute. That hostname would have been specified in the configuration file opensrf.xml, which you configured in a previous step. - [[ explanation for configuring opensrf.xml ]] + + + You can also start Evergreen without the -l flag, but the utility osrf_ctl.sh must know the fully qualified domain name for the system on which it will execute. That hostname may have been specified in the configuration file opensrf.xml, which you configured in a previous step. + + + [[ ADD EXPLANATION FOR CONFIGURING "opensrf.xml" ]] Execute the following command to determine the fully qualified domain name of your system:
(OPTIONAL) Determine the fully qualified domain name @@ -570,7 +624,7 @@ Updating fieldmapper Exception: OpenSRF::EX::Session 2010-04-16T06:31:38 OpenSRF::Utils::SettingsClient /usr/local/share/perl/5.10.0/OpenSRF/Utils/SettingsClient.pm:103 Session Error: router@private.localhost/opensrf.settings IS NOT CONNECTED TO THE NETWORK!!! - [[ TEST THIS! ]] + [[ ADD RESULTS OF TESTS FROM "autogen.sh" ]]
@@ -624,6 +678,7 @@ As the opensrf user, run the script settings-tester.pl to see if it finds any system configuration problems. Following is sample output generated by executing that script after a successful Evergreen installation: + [[ MAY NEED TO REWORK THIS DIAGRAM TO USE SAME IMAGE STANDARDS AS OTHER CHAPTERS ]]
Executing the script <emphasis> settings-test.pl</emphasis> @@ -647,7 +702,7 @@ By default, the OPAC will live at the URL http://my.domain.com/opac/. Navigate to this URL and the front page of the OPAC should load. There is a basic text entry field with some extra search options. If you have any problems loading this page, check the Apache error logs. If the page loads but does not function correctly, then check for possible javascript errors. We hightly reccommend testing with the Firefox browser because of the helpful javascript debugging tools. Assuming that the OPAC is functioning and there is data in your database, you can now perform other simple functional tests (e.g., searching the catalog). - [[ other simple functional tests ]] + [[ ADD OTHER SIMPLE FUNCTIONAL TESTS ]]
Other Tests with srfsh @@ -663,6 +718,23 @@ For other srfsh commands, type 'help' in at the prompt.
+
+ Post-Installation Chores + + + As the root user, edit the Apache configuration file /etc/apache2/sites-available/eg.conf again and make the following change: + Uncomment the line Allow from 10.0.0.0/8, then comment out the line Allow from all. You modified this file earlier in step 5.1.15 as a temporary measure to expedite testing. Those changes must now be reversed in order to deny access to your CGI scripts by other public networks. You must secure this for a public production system, preferably by explicitly specifying the allowed IP addresses and adding proper authentication. + + + + + This is only a temporary measure to expedite testing. You must get a proper SSL certificate for a public production system. See this section for further comments on setting up a properly signed SSL certificate: + + + [[ ADD EXPLANATION OF HOW TO GET A SIGNED SSL CERTIFICATE ]] + + +
Running the Staff Client on Linux Run the Evergreen Staff Client on a Linux system by using the application XULRunner (installed automatically and by default with Firefox version 3.0 and later on Ubuntu and Debian distributions). @@ -700,8 +772,12 @@ $ osrf_ctl.sh -l -a stop_all - Note: You can also stop Evergreen services without the -l flag, but the utility osrf_ctl.sh must know the fully qualified domain name for the system on which it will execute. That hostname would have been specified in the configuration file opensrf.xml, which you configured in a previous step. - [[ explanation for configuring opensrf.xml ]] + + + You can also stop Evergreen services without the -l flag, but the utility osrf_ctl.sh must know the fully qualified domain name for the system on which it will execute. That hostname may have been specified in the configuration file opensrf.xml, which you configured in a previous step. + + + [[ ADD EXPLANATION FOR CONFIGURING "opensrf.xml" ]]
Setting Up Support For Reports @@ -729,7 +805,12 @@
Stopping the Reporter Daemon - To stop the Reporter daemon, you must kill the process and remove the lockfile. The daemon may have just a single associated process, with a lockfile in the default location. Note: it is possible that several processes are running; see the optional commands in the previous section. As the opensrf user, perform the following commands to stop the Reporter daemon: + To stop the Reporter daemon, you must kill the process and remove the lockfile. The daemon may have just a single associated process, with a lockfile in the default location. + + + It is possible that several processes are running; see the optional commands in the previous section. As the opensrf user, perform the following commands to stop the Reporter daemon: + +
Stopping the Reporter Daemon @@ -744,7 +825,7 @@
Installing OpenSRF - [[ Installing OpenSRF 1.2.x ]] + [[ Installing OpenSRF 1.2.2 ]]
Installing Evergreen On Other Linux Systems @@ -787,10 +868,6 @@ Installing the Staff Client [[ Installing the Staff Client ]]
-
- Adding Language Localization - [[ Adding Localized Languages to the Database ]] -
Installing the SIP Server [[ Installing the SIP Server ]] -- 2.43.2