[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cvs tag and #cvs.lock
From: |
Paul Edwards |
Subject: |
Re: cvs tag and #cvs.lock |
Date: |
Sun, 04 May 2003 00:28:28 GMT |
"Larry Jones" <lawrence.jones@eds.com> wrote in message
news:mailman.5533.1051984031.21513.bug-cvs@gnu.org...
> Paul Edwards writes:
> >
> > On CVS 1.11.5 on Solaris someone did a "cvs tag" (not rtag)
> > and then ctrl-c'd it, and it left a #cvs.lock in the repository.
> >
> > This is a local repository.
> >
> > Does CVS not handle this cleanly?
>
> It's supposed to -- it works for me. All I can think of is that someone
> did something more drastic than ctrl-c (like ctrl-\) or managed to do
> ctrl-c a second time before CVS had finished cleaning up.
Multiple ctrl-c's are something that is often seen done by
Unix types (although I don't know about this specific instance).
Should a sig-ignore be done whenever the ctrl-c handler is
invoked to handle "common user practice"? Or a handler
that says "stop interrupting me, I'm working as fast as I can
on the original instruction"?
BFN. Paul.