X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.4 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4C6BDD79.5050307@redhat.com>
References: <AANLkTin6rup-PmQj2yCXgEBUajHhQ_J73UstwmLht-sa AT mail DOT gmail DOT com>	<4C6B5191 DOT 7070602 AT cygwin DOT com>	<AANLkTin8J=k9bbw7q8LTD4S7+XdT61W5fuShYdgbzf4j AT mail DOT gmail DOT com>	<20100818055204 DOT GA19288 AT ednor DOT casa DOT cgf DOT cx>	<20100818085754 DOT GP11340 AT calimero DOT vinschen DOT de>	<445852471 DOT 20100818142802 AT mtu-net DOT ru>	<20100818110852 DOT GS11340 AT calimero DOT vinschen DOT de>	<4C6BDD79 DOT 5050307 AT redhat DOT com>
Date: Wed, 18 Aug 2010 21:51:29 +0800
Message-ID: <AANLkTinesfa8RzGjDsAV9oaEc1WNfPM1=mC3b+_u8Bds@mail.gmail.com>
Subject: Re: cygwin 1.7 lock directory problem
From: Huang Bambo <bambo DOT huang AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

2010/8/18 Eric Blake <eblake AT redhat DOT com>:
> On 08/18/2010 05:08 AM, Corinna Vinschen wrote:
>>>> Looks like this behaviour is a problem and we should better close the
>>>> old handle. =A0What to do with the new one? =A0Just set it to NULL and
>>>> disallow stackdumps as long as we're in a virtual path? =A0Or set it to
>>>> some well known path, like Cygwin's root?
>>>
>>> /var or /tmp would be more sensible.
>>
>> Maybe, but it also costs time. =A0/var and /tmp Windows paths have to be
>> generated by a full path conversion every time you call chdir() to a
>> virtual directory.
>> The Cygwin installation path (aka the root dir) is just available.
>
> Using / as the fallback during a virtual directory makes sense to me
> (there may be other permission problems if / is not writable by the
> current user, but a stack dump is a best effort attempt anyways).
>
Even in linux, you can't generate core file in virtual directory also,
so just don't generate core file if you can't write at anywhere.

--
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