From: Mel Hatzis <hatzis@juniper.net>
To: Chandra Ramesh <Ramesh.Chandra@siemens.com>
Cc: GNATS HELP <help-gnats@gnu.org>
Subject: Re: PR Submission (Change of state) gets locked
Date: Mon, 27 Jan 2003 07:41:00 -0000 [thread overview]
Message-ID: <3E34DD76.3000908@juniper.net> (raw)
In-Reply-To: <892CE977BB4FD31194EE00A0C9F2733909DF5323@blrk001a.sisl.co.in>
On 01/26/2003 10:50 PM, Chandra Ramesh submitted:
>
> Hello,
>
> We are having Gnats 3.113.1 on a RED HAT 7.3 Linux OS.
>
> When we edit a PR for a state change and click on the "click
> here to submit the changes" button,
> we are getting an error saying:
>
> "Your problem report changes have not been sent"
> problem report Config/6 is being edited by Ramesh.
>
> In the above error "Config" is a category and 6 is the PR
> number assigned.
> It is me (Ramesh) who is changing the state and when I submit
> the changes, I am getting the above error.
> In the "locks" directory, there is a "6.lock" file which gets
> created.
>
> I am running the "gnatsd" daemon through xinetd.
>
> How can I solve this problem? Please let me know.
>
> Thanks and Regards,
> Ramesh Chandra
>
It appears that you have a stale lock file (the 6.lock file in the locks
directory)
that is preventing you from submitting updates. Delete the lock file and try
your PR update again.
Stale lock files can result if an edit is abnormally terminated....say,
by killing
an edit-pr process during an edit.
Hope this helps.
--
Mel Hatzis
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2003-01-27 7:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 7:02 Chandra Ramesh
2003-01-27 7:41 ` Mel Hatzis [this message]
2003-01-27 9:51 Chandra Ramesh
[not found] <892CE977BB4FD31194EE00A0C9F2733909DF574A@blrk001a.sisl.co. in>
2003-01-27 9:56 ` Yngve Svendsen
2003-01-28 10:16 Chandra Ramesh
2003-01-28 10:26 ` Michael Loftis
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=3E34DD76.3000908@juniper.net \
--to=hatzis@juniper.net \
--cc=Ramesh.Chandra@siemens.com \
--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).