653 |
@cindex using @sc{gnats} over a network |
@cindex using @sc{gnats} over a network |
654 |
@cindex configuring @sc{gnats} on a network |
@cindex configuring @sc{gnats} on a network |
655 |
|
|
656 |
When you install the @sc{gnats} utilities, the user tools are installed |
When you install the @sc{gnats} utilities, the user tools are |
657 |
by default on the host machine. If your machine is part of a network, |
installed by default on the host machine. If your machine is part of |
658 |
however, you may wish to install the user tools on each machine in the |
a network, however, you may wish to install the user tools on each |
659 |
network so that responsible parties on those machines can submit new |
machine in the network so that responsible parties on those machines |
660 |
Problem Reports, query the database, and edit existing PRs. To do this, |
can submit new Problem Reports, query the database, and edit existing |
661 |
follow these steps @emph{on each new host}. You may need @code{root} access on |
PRs. |
|
each machine. |
|
662 |
|
|
663 |
(still to be written...) |
In the following discussion, machines with the @sc{gnats} user |
664 |
@c XXXXX Need to document the new network features. |
tools installed are referred to as @dfn{client} machines. |
665 |
|
|
666 |
|
As discussed below, there are two main ways to make the user tools |
667 |
|
available on client hosts, depending on where the client machines are |
668 |
|
located. |
669 |
|
|
670 |
|
@subsection User tools on a local network |
671 |
|
@cindex using @sc{gnats} over a local network |
672 |
|
@cindex configuring @sc{gnats} on a local network |
673 |
|
|
674 |
|
If all the machines involved reside on the same local network |
675 |
|
as the @sc{gnats} server, you can simply share out the directories on |
676 |
|
the server that contain the user tools, by default |
677 |
|
@file{/usr/local/bin} and the directory which contains the |
678 |
|
@file{send-pr.conf} configuration file, by default |
679 |
|
@file{/usr/local/etc/gnats}. If you have a heterogeneous environment, |
680 |
|
i.e. hosts running different operating systems, you need to create |
681 |
|
several shared @sc{gnats} installations. The @file{send-pr.conf} file |
682 |
|
is platform-independent, though. |
683 |
|
|
684 |
|
In order to submit a new PR, @code{send-pr} would then be invoked as |
685 |
|
follows on the client machines: |
686 |
|
|
687 |
|
@smallexample |
688 |
|
send-pr -d @var{hostname:port:database:username:password} |
689 |
|
@end smallexample |
690 |
|
|
691 |
|
Or by first setting the environment variable @code{GNATSDB} as follows |
692 |
|
(the exact syntax will vary depending on what shell you use): |
693 |
|
|
694 |
|
@smallexample |
695 |
|
export GNATSDB=@var{hostname:port:database:username:password} |
696 |
|
@end smallexample |
697 |
|
|
698 |
|
Then, @code{send-pr} can simply be invoked without any options. |
699 |
|
|
700 |
|
@subsection User tools for remote users |
701 |
|
@cindex using @sc{gnats} remotely |
702 |
|
@cindex configuring @sc{gnats} for remote users |
703 |
|
|
704 |
|
Outline for each host: |
705 |
|
|
706 |
|
@enumerate |
707 |
|
@item Download |
708 |
|
@item Configure |
709 |
|
@item make |
710 |
|
@item Install send-pr.conf |
711 |
|
@end enumerate |
712 |
|
|
713 |
|
Use same send-pr syntax as above or use GNATSDB, OR for sites that |
714 |
|
need to submit by e-mail, create a template by running ``send-pr -p'' |
715 |
|
and install this file on the clients. |
716 |
|
|
717 |
@c --------------------------------------------------------------- |
@c --------------------------------------------------------------- |
718 |
@node Upgrading |
@node Upgrading |