From: Yngve Svendsen <yngve.svendsen@sun.com>
To: Chandra Ramesh <Ramesh.Chandra@siemens.com>, hatzis@juniper.net
Cc: GNATS HELP <help-gnats@gnu.org>
Subject: RE: PR Submission (Change of state) gets locked
Date: Mon, 27 Jan 2003 09:56:00 -0000 [thread overview]
Message-ID: <5.2.0.9.0.20030127104700.02af72c0@ms-etro01-01.norway.sun.com> (raw)
In-Reply-To: <892CE977BB4FD31194EE00A0C9F2733909DF574A@blrk001a.sisl.co. in>
At 14:26 27.01.2003 +0530, Chandra Ramesh wrote:
>Hello,
>
> The lock file is not a stale file. It is getting created every time
> the moment I click on the submit button after entering the reqd
> changes.
>
> Probably, the lock file should be created to prevent a
> simultaneous modification
> by an other user. The problem is that the lock file should get
> deleted on it's own
> and but it is not.
This probably means that gnatsd crashes while processing your changes. Have
you made any changes to the database config files (categories etc.) lately?
gnatsd 3.x does not handle syntax errors there gracefully and may leave
stale lock files behind when it dies. You should probably have a look at
your config.
Yngve Svendsen
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next parent reply other threads:[~2003-01-27 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <892CE977BB4FD31194EE00A0C9F2733909DF574A@blrk001a.sisl.co. in>
2003-01-27 9:56 ` Yngve Svendsen [this message]
2003-01-28 10:16 Chandra Ramesh
2003-01-28 10:26 ` Michael Loftis
-- strict thread matches above, loose matches on Subject: below --
2003-01-27 9:51 Chandra Ramesh
2003-01-27 7:02 Chandra Ramesh
2003-01-27 7:41 ` Mel Hatzis
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=5.2.0.9.0.20030127104700.02af72c0@ms-etro01-01.norway.sun.com \
--to=yngve.svendsen@sun.com \
--cc=Ramesh.Chandra@siemens.com \
--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).