Re: use of GNATSDB

[Dirk Bergstrom]

On 5/17/2002 11:13 AM, this issued forth from the mind of Lars Henriksen:
> 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. 

i guess i wasn't very clear in my explanation:

using pr-edit in localhost mode, it is IMPOSSIBLE to lock ANY database.

the program locks the db, then unlocks it a few lines later.  it's a bug
in the localhost mode code, one of many.

-- 
Dirk Bergstrom                   address@hidden
Computer Geek                     v: 707.433.0564
Juniper Networks Inc.             f: 707.433.0769

"it *looks* like a nail; lemme grab my hammer..."