Christopher Faylor <cgf-use-the-mailinglist-please <at> cygwin.com> writes: On Sun, Jun 10, 2007 at 10:16:41PM +0000, Mark Geisert wrote: > [original question and my incorrect analysis elided...] > > ...and if all Cygwin processes are subsequently exited then it isn't > Cygwin's fault either. Let's not go down this path again. Cygwin has > no magical powers to make Windows permanently use memory. Look to > resident third-party software to perform this feat, not Cygwin. > > cgf
Of course you're correct here CGF; sorry for the noise. My home systems and work systems that show the problem have different sets of resident 3rd-party software, none of which seem to be on the Known Bad Apps list. I jumped to the wrong conclusion. The depressing alternate conclusion is that there are more Bad Apps to be added to the list. I'll see if I can figure out what those are. Thanks, ..mark -- 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/
