Hi Marco, It is in the changelog of the version 1.3:
http://www.ossec.net/announcements/v1.3-2007-08-08.txt " -Fixed file descriptor leak on the Windows agent while reading the Windows registry. (Reported by Luke Bradeen <lbradeen at suresource.com>) " Thanks, -- Daniel B. Cid dcid ( at ) ossec.net On 10/24/07, Marco Supino <[EMAIL PROTECTED]> wrote: > > > > > Where can I find this info ? I couldn't find anything in the changelog > > > > Marco. > > > > > > > > From: ossec-list@googlegroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of McClinton, Rick > Sent: Wednesday, October 24, 2007 17:05 > To: ossec-list@googlegroups.com > Subject: [ossec-list] Re: Ossec on windows > > > > > Yes, It is due to a resource pool leak in those versions. Upgrade to 1.3. > > > > > > > > > ________________________________ > > > From: ossec-list@googlegroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Marco Supino > Sent: Wednesday, October 24, 2007 10:47 AM > To: ossec-list@googlegroups.com > Subject: [ossec-list] Ossec on windows > Importance: Low > > > > Hi, > > > > I am having a problem with Ossec running on windows, versions 1.1 and 1.2, > the machine stops working after a few weeks, > > > > The windows is running an agent connected to a central server. > > > > Messages like "not enough server storage is available to process this > command" and things like that start showing up in the logs, > > > > I am not positive this is because of Ossec, but this has started happening > on machines running it, > > > > Anyone else experience things like this ? > > > > Thanks > >
