From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8187 invoked from network); 17 May 2002 12:06:14 -0000 Received: from unknown (HELO fencepost.gnu.org) (199.232.76.164) by sources.redhat.com with SMTP; 17 May 2002 12:06:14 -0000 Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 178gUl-0005d1-00; Fri, 17 May 2002 08:06:03 -0400 Received: from cluster2.netman.dk ([193.88.72.48]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 178gT9-0005ZE-00 for ; Fri, 17 May 2002 08:04:23 -0400 Received: (from lh@localhost) by cluster2.netman.dk (8.11.4/8.11.4) id g4HC38j1521904; Fri, 17 May 2002 14:03:08 +0200 (MEST) From: Lars Henriksen To: Mel Hatzis Cc: help-gnats@gnu.org Subject: Re: use of GNATSDB Message-ID: <20020517120308.GA1524344@cluster2.netman.dk> References: <3CA28C27.6010201@juniper.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CA28C27.6010201@juniper.net> User-Agent: Mutt/1.3.25i Sender: help-gnats-admin@gnu.org Errors-To: help-gnats-admin@gnu.org X-BeenThere: help-gnats@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: General discussion about GNU GNATS List-Archive: Date: Fri, 17 May 2002 05:06:00 -0000 X-SW-Source: 2002-q2/txt/msg00041.txt.bz2 On Wed, Mar 27, 2002 at 07:21:11PM -0800, Mel Hatzis wrote: > 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. I can't reproduce this behaviour. Whether GNATSDB is set or not, the command "pr-edit --lockdb" seems to lock nothing at all. Neither does "pr-edit --database= --lockdb". On the other hand, "pr-edit --lock " honors GNATSDB as well as the --database option. > 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. There must be more to it than that, but I haven't yet been able to figure out what. Lars Henriksen _______________________________________________ Help-gnats mailing list Help-gnats@gnu.org http://mail.gnu.org/mailman/listinfo/help-gnats