X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: Jim Meyering To: Eric Blake Cc: cygwin AT cygwin DOT com, bug-coreutils Subject: Re: "du -b --files0-from=-" running out of memory In-Reply-To: <49296551.4010801@byu.net> (Eric Blake's message of "Sun, 23 Nov 2008 07:14:41 -0700") References: <49296551 DOT 4010801 AT byu DOT net> Date: Mon, 24 Nov 2008 09:25:38 +0100 Message-ID: <87bpw5a5tp.fsf@rho.meyering.net> Lines: 17 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Eric Blake wrote: > [adding the upstream coreutils list] > According to Barry Kelly on 11/23/2008 6:24 AM: >> I have a problem with du running out of memory. >> >> I'm feeding it a list of null-separated file names via standard input, >> to a command-line that looks like: >> >> du -b --files0-from=- Thank you for the report. (thanks, Erik for the Cc) du's --files0-from option reads the entire list of file names into memory before processing the first name. That bug should be fixed very quickly ;-) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/