From: Mel Hatzis <hatzis@juniper.net>
To: shilpa.reddy@wipro.com
Cc: help-gnats@gnu.org
Subject: Re: Regarding installation
Date: Tue, 23 Mar 2004 09:26:00 -0000 [thread overview]
Message-ID: <405FF20E.4030800@juniper.net> (raw)
In-Reply-To: <C1F81E780BC53D44A7C55DC6633F84147B6B88@blr-ec-msg05.wipro.com>
On 03/22/2004 10:39 PM, shilpa.reddy@wipro.com submitted:
> Hello,
>
> Could u please provide me the steps in detail about how to install
> GNATS.
> I am not able to follow the instructions in the manual
>
Please provide more detail on where you are experiencing problems.
Without detailed information it is very difficult to provide you
any assistance.
Briefly, you run './configure', 'make', 'make install', then
'mkdb default' on the GNATS server. You'll probably also want
to edit your /etc/services and /etc/inetd.conf (or xinetd.d/gnats)
files appropriately to start the GNATS server daemon...
don't forget to HUP inetd if you make changes.
If you wish to run GNATS in a client/server configuration, you
should also run './configure', 'make' and 'make install' on the
client machine(s). You should then edit <instdir>/etc/gnats/databases
appropriately on all client machines to point the GNATS client
binaries to the GNATS server. For send-pr to work successfully,
you should use the '--with-submitter' and '--with-organization'
configure options.
--
Mel Hatzis
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Help-gnats mailing list
> Help-gnats@gnu.org
> http://mail.gnu.org/mailman/listinfo/help-gnats
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
prev parent reply other threads:[~2004-03-23 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 6:57 shilpa.reddy
2004-03-23 9:26 ` Mel Hatzis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=405FF20E.4030800@juniper.net \
--to=hatzis@juniper.net \
--cc=help-gnats@gnu.org \
--cc=shilpa.reddy@wipro.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).