delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2013/05/03/16:23:59

X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:date:from:to:subject:message-id:reply-to
:references:mime-version:content-type:in-reply-to; q=dns; s=
default; b=CjT2u8LaMGvzNEpMKlpoSl86SMETtXWN0tGdvIPwq4VQGQokL0WgT
CiUADA+nha7eakOl/I5Hmf6LDCnulcYnItvqeJ2LcEjyVlSf1QBMj1AhhzLYMmx5
5x7gtHh53JYsUDdoiBEQ6ug8WgAUJZXr6VvNT4b6slRgTZucT86Y38=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:date:from:to:subject:message-id:reply-to
:references:mime-version:content-type:in-reply-to; s=default;
bh=OxIRVZ9qhqa2DmTZqEUdhhAhCoU=; b=t5Qp6G51D+Yrv/BM9DyWUoW94k4S
W+FIkf5sfwHotCPza0iNbqo8WCt4wFkLuZ3tRRjZ+UpVeZxXSruXjn3PRiyKrY+7
/s3RkhU4zVeo+Pi9Aj9c6NlFqu0TRsId+dCxj7uzm8ilv7ob4HnPvqJ7AwduQmMi
9AxHQKNGs8JNPnU=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RCVD_IN_SEMBACKSCATTER autolearn=no version=3.3.1
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1++VZTVpK9L9J3Cabhk6NvT
Date: Fri, 3 May 2013 16:23:40 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: last snapshot: could not acquire lock
Message-ID: <20130503202340.GA5960@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <a2060ff29bb041356a1524baaee14123 AT denis-excoffier DOT org>
MIME-Version: 1.0
In-Reply-To: <a2060ff29bb041356a1524baaee14123@denis-excoffier.org>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, May 02, 2013 at 08:58:44AM +0200, Denis Excoffier wrote:
>Hello,
>
>Snapshot dated 20130430 was working OK for me. Snapshot dated 20130501 
>hangs temporarily (about 40 sec) before
>printing the following message:
>
>       5 [sig] tcsh 2428 get_proc_lock: Couldn't acquire 
>sync_proc_subproc for(5,1), last 7, Win32 error 0
>     194 [sig] tcsh 2428 proc_subproc: couldn't get proc lock. what 5, 
>val 1

This should be fixed in the next snapshot.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019