Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <41FBD281.2020108@x-ray.at>
Date: Sat, 29 Jan 2005 19:14:25 +0100
From: Reini Urban <rurban AT x-ray DOT at>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7) Gecko/20040616
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: pthreads leaks handles and threads when threads use sockets
References: <000c01c5055c$23818cb0$173ca8c0 AT AlohaSunset DOT com>
In-Reply-To: <000c01c5055c$23818cb0$173ca8c0@AlohaSunset.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Mark Pizzolato schrieb:
> I've been using clamav's clamd under cygwin and noticed that over time 
> the handle count as viewed with TaskManager seems to grow to arbitrary 
> values. I used clamd's option IdleTimeout set to 600 seconds which 
> dramatically reduced the growth rate of the Handle Count. Of course 
> clamd has many things going on that could contribute to handle leakags, 
> so I tried to write a simple program to demonstrate the problem.

Thanks a lot! Maybe we should restart the two daemons daily or weekly?

I will change the default IdleTimeout to 600 secs with the upcoming 
clamav-0.81 release. Which fixes the freshclam proxy problem and some 
OLE issues.

But I need some more time (with the postgresql-8.0 release also), 
because we are just moving our office and so I'm loaded with work.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

--
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/