X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Wed, 6 Jun 2012 18:12:17 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Windows 8 Release Preview. fork problems with rsync Message-ID: <20120606161217.GB30795@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20120606123434.GA27662@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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