We didn't. Oops still can't work smoothly on our box, including Linux 2.4.23 & 2.6.0 and FreeBSD 4.9 & 5.2.
If we use some program to test it (like grubclient: http://www.grub.org/), then the memory leak problem will quickly be seen. If we just use it normally (use auto-proxy configuration to set *.org to this Oops box), the problem will be seen about 1 week later. Not only memory leak, but unstable performance: sometimes it can perform 1000reqs/sec (set * to Oops box and also use grubclient to test it), but more than usual, just 100reqs/sec. When we change platform from Linux to FreeBSD, Oops will crash once we run grubclient to test. My suggestion is, if your Oops box has the same problem, don't use Oops. Construct several squid box and auto-proxy configuration, or just buy hardware proxy server. It will save your time. On Thu, Jan 22, 2004 at 07:28:51PM +0500, Berkeley Altiev wrote: > Hello gslin, > > How you resolved you problem with memory leak. I have same trouble. > > -- > Best regards, > Berkeley mailto:[EMAIL PROTECTED] -- * Gea-Suan Lin (public key: http://ccreader.nctu.edu.tw/~gslin/key.txt) * If you cannot convince them, confuse them. -- Harry S Truman ===================================================================== If you would like to unsubscribe from this list send message to [EMAIL PROTECTED] with "unsubscribe oops" in message body. Archive is accessible on http://lists.paco.net/oops-rus/
