X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0	tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL,TW_RV,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Message-ID: <4FD0BC4C.1070603@cs.utoronto.ca>
Date: Thu, 07 Jun 2012 10:35:56 -0400
From: Ryan Johnson <ryan DOT johnson AT cs DOT utoronto DOT ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Windows 8 Release Preview. fork problems with rsync
References: <CAOLRrpGi-OaejySZ82AVDVzt01mPd0A6gWgjaN60W-sqHZG8cw AT mail DOT gmail DOT com> <20120606123434 DOT GA27662 AT calimero DOT vinschen DOT de> <CAOLRrpHQV2JcaK_f1UAEFR33ga=w8hqdNUSEqfZj1ygKXMCVoA AT mail DOT gmail DOT com> <20120606161217 DOT GB30795 AT calimero DOT vinschen DOT de>
In-Reply-To: <20120606161217.GB30795@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

On 06/06/2012 12:12 PM, Corinna Vinschen wrote:
> On Jun  6 16:41, Bertrand Latinville wrote:
>> I'm using
>>
>>   rsync --chmod=ug=rwX -arvz --prune-empty-dirs  --include="*/"
>> --include-from=include-file.txt  --exclude="*" ${source_dir}/
>> ${dest_dir}
> Thanks.  I can confirm the effect.  For no apparent reason, the OS
> reserves a 1 Megs shared memory region, top-down allocated, of which it
> uses about 20K.  It's not the PEB or one of the TEBs, though.  Nor is
> it a thread stack.  I checked, and it turns out that it's allocated
> in every process, on 32 and 64 bit systems.  That's kind of worrying
> since that's bound to collide with mmaped regions and pthread stacks a
> lot.  I don't know what to do at this point.
Given that the OS always gets there first, why not just adjust Cygwin's 
definition of "top" for win8? Or does heap randomization move that 
mystery chunk around?

Ryan


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