> Seems like your saying that (using a car analogy) he should replace the > carberator when the real problem is a leak in the fuel line. (IOW > you're attacking the wrong area - your problem lies elsewhere).
Nope - gotta lower your expectations. I use to work in shop when I was in high school. Bascially I'd snip the line at the leak, get a piece of rubber hose and a couple of hose clamps. Back on the road in five minutes!! - Oh but that's not SAFE ( you may counter ) ( to which I would say ) - neither are crashing servers ... Assuming of course we stick to your analogy and assume that I can't 'replace' the fuel line because - well - it's "Ford's" problem ..... You see, basic people (clueless) are very practical. Why put in a new engine when a piece of duct tape will do??? "Andrew DeFaria" <[EMAIL PROTECTED]>@cygwin.com on 08/07/2003 02:58:10 PM Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Brian Kelly/WTC1/Empire) Subject: Re: Win2k and cygwin memory leak [EMAIL PROTECTED] wrote: > Gosh, isn't there a *win* in *cygwin*?? Not that I'm "demanding" > anything or goodness knows, making suggestions about how you 'Oh Great > One' should allocate your resources - goodness *no*! But this notion > that a WinDoze problem is not *also* a cyg*win* problem - is quite a > *CURIOUS* one to this *clueless* simpleton - INDEED!! Sticking three letters in a name does not make Cygwin == Windows. It is the job of the OS to manage memory not the job of the program. When a process ends the OS is responsible for cleaning up any of the resources that the process aquired. If the OS fails to do this then it's the OS that needs to be fixed, not the process. > Seems in a way that you're saying "I don't care if what I built > doesn't work for this or that because it's Microsoft's problem". Seems like your saying that (using a car analogy) he should replace the carberator when the real problem is a leak in the fuel line. (IOW you're attacking the wrong area - your problem lies elsewhere). > I really don't think you as one who is quick to let Microsoft define > what he can and can't do - as you yourself have said Are you asking Cygwin to re-write and take control of management of memory from the OS?!? That's like asking the carberator mechanic to build his own fuel line running outside the body of the car! > So indeed you pick and choose which *Microsoft* problems to fix that > keep cyg*win* from working - all along *denying* it's a cyg*win* > problem ..... Yes because some problems are fixable or are within the domain of where Cygwin has proper control. You can fix a carberator to get extra house power but if the main engine only has 2 cyclinders don't ask the carberator mechanic to get 8 cyclinder performance - talk to the maker of the engine itself! > Interesting how a 'Great' mind works ;-) ..... Interesting how a clueless mind wanders off... -- 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/ "WellChoice, Inc." made the following annotations on 08/07/2003 03:45:09 PM ------------------------------------------------------------------------------ Attention! This electronic message contains information that may be legally confidential and/or privileged. The information is intended solely for the individual or entity named above and access by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Release/Disclosure Statement -- 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/