Ignore:
Timestamp:
May 16, 2007, 2:19:54 PM (16 years ago)
Author:
Martin Svensson
Message:

Fixes #594 Read "Appendix:base.config ref"

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/doc/src/docbook/appendix/base.config.xml

    r3340 r3347  
    158158        be left empty. Postgres supports schemas and we recommend that the dynamic
    159159        part is created in it's own schema to avoid mixing the dynamic tables with
    160         the regaular ones.
     160        the regular ones.
    161161        </para>
    162162      </listitem>
    … …  
    168168        <para>
    169169        The username to connect to the database. The user should have full permission
    170         to the both the regular and the dynamic database.
     170        to both the regular and the dynamic database.
    171171        </para>
    172172      </listitem>
    … …  
    198198      <listitem>
    199199        <para>
    200         The location of an to an XML file which contains database-specific
     200        The location of an XML file which contains database-specific
    201201        queries overriding those that doesn't work from the
    202202        <filename>/common-queries.xml</filename> file. Use:
    … …  
    274274    <para>
    275275      This section describes parameters that are needed if you are
    276       going to use external authenitcation. If you let BASE handle this
    277       you will not have to bother about theese settings. See
     276      going to use external authentication. If you let BASE handle this
     277      you will not have to bother about these settings. See
    278278      <xref linkend="plugin_developer.other.authentication"/> for more information about
    279279      external authentication.
    … …  
    350350      less in the order they were added to the queue. To make sure long-running
    351351      jobs don't block the queue, there are four slots that uses to the
    352       expected execution time to decide if a job should be allowed to excute
     352      expected execution time to decide if a job should be allowed to execute
    353353      or not.
    354354    </para>
    … …  
    426426        <para>
    427427        Number of seconds to keep job agent information in the internal cache.
    428         The information includs, CPU and memory usage and the status of executing
     428        The information includes, CPU and memory usage and the status of executing
    429429        jobs. This setting controls how long the information is kept in the cache
    430430        before a new request is made to the job agent. The default value is 60 seconds.
    … …  
    437437      <listitem>
    438438        <para>
    439         The timeout in milliseconds to wait for a repsonse from a job agent
     439        The timeout in milliseconds to wait for a response from a job agent
    440440        when sending a request to it. The default timeout is 1000 milliseconds.
    441441        This should be more than enough if the job agent is on the internal
    … …  
    476476      <listitem>
    477477        <para>
    478         Initialisation paramters sent to the plug-in when calling the
     478        Initialisation parameters sent to the plug-in when calling the
    479479        <methodname>init()</methodname> method. The syntax and meaning of this
    480480        string depends on the plug-in. For the internal controller this is simply
    481         the path to the seconday directory.
     481        the path to the secondary directory.
    482482          </para>
    483483      </listitem>
    … …  
    502502        should be executed. If present, this setting overrides the
    503503        <property>secondary.storage.interval</property> setting.
    504         Time-point values are given as comma-separted list of two-digit, 24-based hour
     504        Time-point values are given as comma-separated list of two-digit, 24-based hour
    505505        and two-digit minute values. For example: <userinput>03:10,09:00,23:59</userinput>.
    506506          </para>
    … …  
    550550      </listitem>
    551551    </varlistentry>
     552    <varlistentry>
     553      <term><property>helptext.update</property></term>
     554      <listitem>
     555        <para>
     556          Defines if already existing helptexts in BASE should be overwritten when
     557          updating the program,
     558          <xref linkend="installation_upgrade.upgrade" />
     559          <itemizedlist>
     560            <listitem>
     561              <simpara>
     562                <userinput>true</userinput>
     563                will overwrite existing helptexts.
     564              </simpara>
     565            </listitem>
     566            <listitem>
     567              <simpara>
     568                <userinput>false</userinput>
     569                will leave the existing helptexts in database unchanged and only
     570                insert new helptexts.
     571              </simpara>
     572            </listitem>
     573          </itemizedlist>
     574        </para>
     575      </listitem>
     576    </varlistentry>
    552577    </variablelist>
    553578  </simplesect>
Note: See TracChangeset for help on using the changeset viewer.