Message-Id: <200505162124.j4GLOGuE006374@delorie.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: "Gary R. Van Sickle" To: Subject: RE: More: Recent increase in size Date: Mon, 16 May 2005 16:27:09 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: X-IsSubscribed: yes > -----Original Message----- > From: Igor Pechtchanski [snip] > > On Mon, 16 May 2005, Gary R. Van Sickle wrote: > > > > -----Original Message----- > > > From: cygwin-owner AT XXXXXX DOT XXX > > > [mailto:cygwin-owner AT XXXXXX DOT XXX] On Behalf Of fergus > > Tut-tut... ... > ...? I was under the impression that cygwin{}@'s weren't an issue; if they're harvesting from the list, they already have it anyway, right? [snip] > > > (And what is the consequence for memory usage when the virtual > > > directories /usr/bin/ and /usr/lib/ are created on startup?) > > > > This I do: Those are just mount table entries. Memory usage won't > > change regardless of the number or size of files in the directory a > > Cygwin mount table entry points to. So there's no > consequence there. > > True for the actual disk space usage. However, if "du -s" is > used from the root, it will traverse both "/bin" and > "/usr/bin", and add up the numbers (so you get the size of > /bin counted twice, same for /lib). > Igor Well, right, but he asked about memory (i.e. RAM) usage. -- Gary R. Van Sickle -- 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/