Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Thu, 30 Mar 2000 23:41:58 -0500 From: Christopher Faylor To: Mumit Khan Cc: Cygwin Developers List Subject: Re: net release/installer status? Message-ID: <20000330234158.A4580@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: Christopher Faylor , Mumit Khan , Cygwin Developers List References: <20000330233152 DOT A4520 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: ; from khan@NanoTech.Wisc.EDU on Thu, Mar 30, 2000 at 10:38:52PM -0600 On Thu, Mar 30, 2000 at 10:38:52PM -0600, Mumit Khan wrote: >On Thu, 30 Mar 2000, Chris Faylor wrote: > >> I just did a cvs update to grab this change but nothing got updated. >> Am I just being impatient or is there a problem? > >It's hitting a lock, and spinning since I sent the mail out. CVS has >certain bugs that will cause a lock left in place when a remote >connection aborts. Could you please check the mingw directory to see >if there's a .#* file there? > >cvs server: [20:21:45] waiting for anoncvs's lock in /cvs/src/src/winsup/mingw >cvs server: [20:22:15] waiting for anoncvs's lock in /cvs/src/src/winsup/mingw >[ ... ] >cvs server: [20:37:44] waiting for anoncvs's lock in /cvs/src/src/winsup/mingw I removed the lock. It was referring to a nonexistent process so you're probably right about the aborted connection. This is at least the second time that something like this has happened in the mingw directory... cgf