From: Wally Kramer <wally@steptech.com>
To: sourcenav@sources.redhat.com
Subject: RE: SN5.0.0: "you already have project xxx open on this machine"
Date: Thu, 14 Mar 2002 13:39:00 -0000 [thread overview]
Message-ID: <26F9F6EAB586D411850700B0D049E6E410BDEC@shasta.pdx.steptech.com> (raw)
Examining the source, I find lock file management in snavigator/db/dbimp.c
line 521
sprintf(lock_file,"%s.lck",db_prefix);
where db_prefix is "directory/project_name". So it appears to create a file
directory/project.lck which contains the user/pid/etc of the locking user.
I don't see any other references to file locking, besides those in this
module.
-----Original Message-----
From: Charles Manning
Sent: Tuesday, 12 March 2002 12:50
Cc: sourcenav@sources.redhat.com
Subject: Re: SN5.0.0: "you already have project xxx open on this
machine"
On Tue, 12 Mar 2002 08:33, Khamis Abuelkomboz wrote:
> I didn't see the reply to your question. It was in the past so, that SN
> has created a .lck file.
> But in the new release the information the project is being opened is
> ?stored? in the
> project file itself.
>
> I came sometimes into this problem and had the only chance to recreate
> the project.
I thought this might be the case:
It would be nice to know which bytes in the file are the lock bytes. That
would allow a fast and nasty way to fix the problem.
>
> khamis
>
> Charles Manning wrote:
> >Thanx for the previous help on this. I sent a thanx message to to the
> > reply address (wally@steptech.com) but that bounced.
> >
> >Anyway I came across the problem again and there was no .lock file in the
> >.snprj directory.
> >I also deleted the ~/.sn stuff. Still no go :-(.
> >
> >
> >Any more pointers?
> >
> >Thanx
> >
> >-- CHarles
next reply other threads:[~2002-03-12 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 13:39 Wally Kramer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-11 8:43 Charles Manning
2002-03-11 13:45 ` Khamis Abuelkomboz
2002-03-12 13:26 ` Charles Manning
2002-03-08 16:11 Charles Manning
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=26F9F6EAB586D411850700B0D049E6E410BDEC@shasta.pdx.steptech.com \
--to=wally@steptech.com \
--cc=sourcenav@sources.redhat.com \
/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).