info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: "Stale" CVS locks


From: Reinstein, Shlomo
Subject: RE: "Stale" CVS locks
Date: Thu, 14 Jun 2001 08:32:04 +0300

Hi,
We work on CVS on both Windows NT/2000 and Linux. Most of the time we work
on Windows, and Windows users are used to Ctrl+Break... Anyway, yesterday
Larry Jones told me I should still send a bug report about this, so I did
that. About SIGQUIT, I don't know, I am not familiar with the Unix signals.
Shlomo

-----Original Message-----
From: address@hidden [mailto:address@hidden
Sent: Wednesday, June 13, 2001 9:44 PM
To: Reinstein, Shlomo
Cc: address@hidden
Subject: RE: "Stale" CVS locks


[ On Wednesday, June 13, 2001 at 08:25:02 (+0300), Reinstein, Shlomo wrote:
]
> Subject: RE: "Stale" CVS locks
>
> Thanks for the info. I would just like to make a small clarification: If
the
> user clicks Ctrl+C, CVS traps the signal and cleans up the locks. However,
> it doesn't do so when the user clicks Ctrl+Break. With this clarification,
> should I still report it as a bug?

I'm assuming your platform is M$?  If so then is <Ctrl><Break> the same
as a tty generated SIGQUIT in Unix (usually a <CTRL><BackSlash>?  If so
then it's not a bug, but rather a "feature".  Users should not get into
the habit of using SIGQUIT unless they are actually attempting to
purposefully crash the program and debug the resulting core dump.

It would be possible, but generally speaking incorrect, for CVS to trap
SIGQUIT.

-- 
                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]