public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Mel Hatzis <hatzis@juniper.net>
To: help-gnats@gnu.org
Subject: use of GNATSDB
Date: Wed, 27 Mar 2002 19:24:00 -0000	[thread overview]
Message-ID: <3CA28C27.6010201@juniper.net> (raw)

I'm trying to setup a separate database instance by adding a line
into the share/gnats/databases file and setting the GNATSDB env
variable to point to it. I can successfully 'telnet localhost port#'
and, say, lockdb, but when I try using pr-edit it ends up locking
the default database.

Grokking through the code, I find that client_init_gnats
in client.c is invoking 'chdb default' because the scanenv function
always sets database to 'default' during initialization.

My question is..."wouldn't it make more sense to do the equivalent of
'database =  getenv ("GNATSDB")' rather than blindly setting it
to 'default'?

--
Mel Hatzis
Juniper Networks Inc.


_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats

             reply	other threads:[~2002-03-28  3:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27 19:24 Mel Hatzis [this message]
     [not found] ` <15525.34645.542865.70528@habakuk.home.ha-schneider.de>
     [not found]   ` <3CA6046B.1060004@juniper.net>
     [not found]     ` <15528.10405.211358.551224@habakuk.home.ha-schneider.de>
2002-04-30 22:18       ` Mel Hatzis
2002-05-17  5:06 ` Lars Henriksen
2002-05-17  5:24   ` Lars Henriksen
2002-05-17  5:30     ` Lars Henriksen
2002-05-17 11:09       ` Mel Hatzis
2002-05-17 11:33         ` Lars Henriksen
2002-05-17 10:33   ` Dirk Bergstrom
2002-05-17 11:15     ` Lars Henriksen
2002-05-17 11:21       ` Dirk Bergstrom

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=3CA28C27.6010201@juniper.net \
    --to=hatzis@juniper.net \
    --cc=help-gnats@gnu.org \
    /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).