This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: net release/installer status?
- To: Mumit Khan <khan at NanoTech dot Wisc dot EDU>
- Subject: Re: net release/installer status?
- From: Christopher Faylor <cgf at cygnus dot com>
- Date: Thu, 30 Mar 2000 23:41:58 -0500
- Cc: Cygwin Developers List <cygwin-developers at sourceware dot cygnus dot com>
- References: <20000330233152.A4520@cygnus.com> <Pine.HPP.3.96.1000330223639.1711C-100000@hp2.xraylith.wisc.edu>
- Reply-To: cygwin-developers at sourceware dot cygnus dot com
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