[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Changes to gnats/doc/p-inst.texi
From: |
Yngve Svendsen |
Subject: |
Changes to gnats/doc/p-inst.texi |
Date: |
Sun, 31 Mar 2002 19:18:12 -0500 |
Index: gnats/doc/p-inst.texi
diff -c gnats/doc/p-inst.texi:1.13 gnats/doc/p-inst.texi:1.14
*** gnats/doc/p-inst.texi:1.13 Sun Mar 31 17:19:38 2002
--- gnats/doc/p-inst.texi Sun Mar 31 19:18:08 2002
***************
*** 653,668 ****
@cindex using @sc{gnats} over a network
@cindex configuring @sc{gnats} on a network
! When you install the @sc{gnats} utilities, the user tools are installed
! by default on the host machine. If your machine is part of a network,
! however, you may wish to install the user tools on each machine in the
! network so that responsible parties on those machines can submit new
! Problem Reports, query the database, and edit existing PRs. To do this,
! follow these steps @emph{on each new host}. You may need @code{root} access
on
! each machine.
! (still to be written...)
! @c XXXXX Need to document the new network features.
@c ---------------------------------------------------------------
@node Upgrading
--- 653,718 ----
@cindex using @sc{gnats} over a network
@cindex configuring @sc{gnats} on a network
! When you install the @sc{gnats} utilities, the user tools are
! installed by default on the host machine. If your machine is part of
! a network, however, you may wish to install the user tools on each
! machine in the network so that responsible parties on those machines
! can submit new Problem Reports, query the database, and edit existing
! PRs.
! In the following discussion, machines with the @sc{gnats} user
! tools installed are referred to as @dfn{client} machines.
!
! As discussed below, there are two main ways to make the user tools
! available on client hosts, depending on where the client machines are
! located.
!
! @subsection User tools on a local network
! @cindex using @sc{gnats} over a local network
! @cindex configuring @sc{gnats} on a local network
!
! If all the machines involved reside on the same local network
! as the @sc{gnats} server, you can simply share out the directories on
! the server that contain the user tools, by default
! @file{/usr/local/bin} and the directory which contains the
! @file{send-pr.conf} configuration file, by default
! @file{/usr/local/etc/gnats}. If you have a heterogeneous environment,
! i.e. hosts running different operating systems, you need to create
! several shared @sc{gnats} installations. The @file{send-pr.conf} file
! is platform-independent, though.
!
! In order to submit a new PR, @code{send-pr} would then be invoked as
! follows on the client machines:
!
! @smallexample
! send-pr -d @var{hostname:port:database:username:password}
! @end smallexample
!
! Or by first setting the environment variable @code{GNATSDB} as follows
! (the exact syntax will vary depending on what shell you use):
!
! @smallexample
! export address@hidden:port:database:username:password}
! @end smallexample
!
! Then, @code{send-pr} can simply be invoked without any options.
!
! @subsection User tools for remote users
! @cindex using @sc{gnats} remotely
! @cindex configuring @sc{gnats} for remote users
!
! Outline for each host:
!
! @enumerate
! @item Download
! @item Configure
! @item make
! @item Install send-pr.conf
! @end enumerate
!
! Use same send-pr syntax as above or use GNATSDB, OR for sites that
! need to submit by e-mail, create a template by running ``send-pr -p''
! and install this file on the clients.
@c ---------------------------------------------------------------
@node Upgrading