
# $Id: CONFIGURATION,v 1.1 2003/10/18 02:03:07 pcurtis Exp $

The jcr configuration consists of two parts. The first part are
those elements needed for the jcr itself, and the second part is the
component's configuration.

The root elm for the jcr is <jcr/>. The following elms configure the
jcr itself

<ip>
  This is the IP address or the hostname of the server to connect
  to.

<port>
  This is the port number to use when connecting to the server.

<host>
  This is the component's hostname for routing purposes. In orther
  words, this is the host portion of the component's JID.

<name>
  This is the 'uplink' name as defined in the 'jabber.xml' file or
  in the <alias/> element in the 'router.xml' (for jabberd 2)

<secret>
  The shared secret used to authenticate this component to the
  server.

<spool>
  The spool directory. In jabberd 1.4, the spool directory is
  specified only as the top directory with the component's host name
  as the sub-directory. In JCR, this is the full path to the actual
  files that are read/written to by the component.

<logdir>
  A path to a directory for the JCR log file. (jcr.log)

<loglevel>
  A mapping of log levels to record to the logfile. The default is
  124. To add 'log_debug' messages to the log file, set this value
  to 255. (also the '-d nnn' command line option)

<logstderr>
  If this element exists, print all loggin to stderr rather than the
  log file. (also the '-s' command line option)

<pidfile>
  Full path and file name for the file that contains the JCR's
  process ID.

<send-buffer>
<recv-buffer>
  Normally, these will not need to be specified. By default, both
  values are set 8192. The 'recv-buffer' is the maximum number of
  bytes that can be read from the server utilizing one read. The
  'send-buffer' is the maximum amount number of bytes that will be
  written back to the server.

  The JCR endeavours to minimize the number of write calls to the
  server by placing as many available packets into a single socket
  write. If there are packets queued to be sent back to the server,
  JCR will put as many are available into a single write up to the
  value of 'send-buffer'.

Command Line options:

<component-binary-name> -c <configuration-file> [-s] [-d nnn] [-B]
  -c (required) 
     the path and file name of the configuration file
  -s 
     Write all logging information to standard out. This overrides
     the setting in the configuration file.
  -d nnn
     Set the logging level to nnn. This overrides the setting in the
     configuration file.
  -B
     Detach and run in background

