From: Philip Blundell <philb@gnu.org>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb@sources.redhat.com
Subject: Re: cvs server: waiting for anoncvs's lock in /cvs/src/src/gdb
Date: Thu, 03 May 2001 05:53:00 -0000 [thread overview]
Message-ID: <E14vIbM-0004ir-00@kings-cross.london.uk.eu.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1010503140324.613J-100000@is>
>Is there any reasonable way to prevent anoncvs from locking the
>repository for prolonged periods of time? I've just committed a small
>change, and now I'm sitting before the terminal for 30 minutes staring at
>``waiting for anoncvs's lock'' messages. And it's not over yet.
If you were stuck for this long, it almost certainly means a CVS process has
died and left a stale lock in the repository. Someone needs to go in and
delete it manually.
The problem isn't specific to anonymous access; that's not to say it mightn't
be a good thing to get anoncvs out of the main repository and on to some kind
of mirror.
p.
prev parent reply other threads:[~2001-05-03 5:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-03 4:05 Eli Zaretskii
2001-05-03 4:26 ` Eli Zaretskii
2001-05-03 5:45 ` Jonathan Larmour
2001-05-03 6:26 ` Eli Zaretskii
2001-05-03 11:05 ` Christopher Faylor
2001-05-03 5:53 ` Philip Blundell [this message]
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=E14vIbM-0004ir-00@kings-cross.london.uk.eu.org \
--to=philb@gnu.org \
--cc=eliz@is.elta.co.il \
--cc=gdb@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