From: Mel Hatzis <hatzis@juniper.net>
To: Lars Henriksen <Lars.Henriksen@netman.dk>
Cc: help-gnats@gnu.org
Subject: Re: use of GNATSDB
Date: Fri, 17 May 2002 11:09:00 -0000 [thread overview]
Message-ID: <3CE54696.4010209@juniper.net> (raw)
In-Reply-To: <20020517122718.GC1524344@cluster2.netman.dk>
Lars Henriksen wrote:
> On Fri, May 17, 2002 at 02:21:49PM +0200, Lars Henriksen wrote:
>
>>On Fri, May 17, 2002 at 02:03:08PM +0200, Lars Henriksen wrote:
>>
>>>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=<db> --lockdb". On the other hand, "pr-edit --lock <user> <PR>"
>>>honors GNATSDB as well as the --database option.
>>>
>>That wasn't the whole story. In fact GNATSDB is honored by pr-edit when
>>you specify a remote database, but not when you specify a local one.
>>
>
> That should have been:
>
> That wasn't the whole story. In fact GNATSDB is honored by "pr-edit --lockdb"
> when you specify a remote database, but not when you specify a local one.
>
> Lars Henriksen
>
Let's clear some things up... the test I'm running is:
GNATSDB=test $gnats_home/libexec/gnats/pr-edit --lockdb
(let's ignore all other uses of GNATSDB and stick with this one)
My $gnats_home/etc/gnats/databases file looks like:
default:Bug database:/usr/local/com/gnatsdb:server.juniper.net:1529
test:GNATS Test:/homes/hatzis/local/gnats/test:server.juniper.net:1529
Let's also define local vs remote...as far as the code is concerned, it's
remote if the line in the databases file defines the server and port number
...as per the last line in databaseSpecIsNetConn which reads:
return (dbEnt->fieldcount > 3) ? 1 : 0;
So, as far as my test is concerned, local mode is not used at all.
When I run the 'pr-edit --lockdb' command, I don't see a gnats.lock
in my test database...
bash-2.03$ ls /homes/hatzis/local/gnats/test/gnats-adm
addresses current index states
categories dbconfig locks/ submitters
classes gnatsd.access responsible
but I do see a gnats.lock file in the default database...
bash-2.03$ ls /usr/local/com/gnatsdb/gnats-adm
addresses classes gnats.lock locks/ states
categories dbconfig gnatsd.access responsible submitters
-Mel
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2002-05-17 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 19:24 Mel Hatzis
[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 [this message]
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=3CE54696.4010209@juniper.net \
--to=hatzis@juniper.net \
--cc=Lars.Henriksen@netman.dk \
--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).