Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Kris Thielemans" To: "Gnuwin" Cc: "Kris Thielemans" Subject: my CVS on NT stopped working Date: Tue, 8 Oct 2002 16:54:26 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Hi, (cross-posted to info-cvs AT gnu DOT org) I'm using CVS 1.11.1p1 on NT 4.0 sp6a (CVS compiled from sources using cygwin). My CVS server is a Linux machine (also running 1.11.1p1). I had a module checked out ages ago and was working happily with it. Now I suddenly get the following error message: $ pwd ~/parapet/PPhead $ cvs -d parapet:/usr/local/cvsroot -t status Makefile -> main loop with CVSROOT=parapet:/usr/local/cvsroot -> Starting server: rsh parapet cvs server -> Sending file `Makefile' to server /#cvs.lock): No such file or directoryctory for `/usr/local/cvsroot/parapet/PPhead 'vs server: failed to obtain dir lock in repository `/usr/local/cvsroot/parapet/PPhead cvs [server aborted]: read lock failed - giving up -> Lock_Cleanup() The jumbled up look of the error message is not an artefact of the mail software. It's really how it comes out. However, when I check out the module again somewhere else, everything works nicely. Even stranger, when I run cvs from in gdb, it works fine. I've tried to upgrade to cvs 1.11.2, but identical problems. Same problem when I use cygwin's cvs version that setup installs (didn't try to gdb trick there) Any ideas? Thanks! Kris Thielemans (kris.thielemans ic.ac.uk) Imaging Research Solutions Ltd Cyclotron Building Hammersmith Hospital Du Cane Road London W12 ONN, United Kingdom web site address: http://www.irsl.org/~kris -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/