public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Lars Henriksen <Lars.Henriksen@netman.dk>
To: Dirk Bergstrom <dirk@juniper.net>
Cc: Mel Hatzis <hatzis@juniper.net>, help-gnats@gnu.org
Subject: Re: use of GNATSDB
Date: Fri, 17 May 2002 11:15:00 -0000	[thread overview]
Message-ID: <20020517181303.GA1558598@cluster2.netman.dk> (raw)
In-Reply-To: <3CE53E5E.2080402@juniper.net>

On Fri, May 17, 2002 at 10:31:10AM -0700, Dirk Bergstrom wrote:
> On 5/17/2002 5:03 AM, this issued forth from the mind of Lars Henriksen:
> > 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.
> 
> this is a totally different issue.

Is it? The issue is how or whether GNATSDB is honered by (for example) pr-edit
and it was claimed, without reservations, that it always ended up locking
the default database. As far as I can see, you confirm below that this is
not the case. 

> so in pr-edit, the "network mode" lockdb code opens a socket to gnatsd
> and issues a LKDB command, and gnatsd locks the database.

...

>                                                           in "localhost
> mode", pr-edit makes a call to gnats_lock() (actually, it calls foo,
> which calls bar, which calls gnats_lock), which is the same call that
> gnatsd makes.  this *does* lock the database, but then, at the very end
> of main(), there's a check that says something like:
> 
> if (gnats_locked) {
>     unlock_gnats()
> }
> 
> this check is entirely reasonable, if you're trying to do an edit, or an
> append, but it's just wrong if you're trying to lock the database.

Thanks for the explanations. They agree with my observations.

> so, you happen to have run into one of the many, many subtle and
> outrageous bugs in localhost mode.  this is why i counsel people to
> *always* use network mode, even when talking to a local database.

But of course you are right that this behaviour has nothing to do with GNATSDB.

> how, you ask, do you make sure you're using network mode?  by specifying
> either --host or --port or both.

Or by setting GNATSDB to point to the remote database.

Lars Henriksen

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

  reply	other threads:[~2002-05-17 18:15 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
2002-05-17 11:33         ` Lars Henriksen
2002-05-17 10:33   ` Dirk Bergstrom
2002-05-17 11:15     ` Lars Henriksen [this message]
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=20020517181303.GA1558598@cluster2.netman.dk \
    --to=lars.henriksen@netman.dk \
    --cc=dirk@juniper.net \
    --cc=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).