similar to: win32-eventlog-0.2.1 released

Hi all, I released win32-eventlog 0.4.5 today. It''s still a bit on the slow side. The profiler (and general testing) indicates that it''s line 696 that''s the major culprit: va_list = str.split(0.chr)[0...num] Other than changing 0.chr to a literal "\0", does anyone have a way to speed this up? It''s not crucial, but I thought it might make a nice

Hi all, I''ve logged a new bug for win32-eventlog based on Joey Gibson''s ruby talk post (116528). Park, I''ve assigned it to you for now, figuring that you''re probably the one who best knows how to fix it. All help welcome. Dan

Thank you very much. :) Dan > -----Original Message----- > From: win32utils-devel-bounces@rubyforge.org > [mailto:win32utils-devel-bounces@rubyforge.org] On Behalf Of > win32utils-devel@rubyforge.org > Sent: Friday, October 29, 2004 7:12 PM > To: win32utils-devel@rubyforge.org > Subject: Re:[Win32utils-devel] buffer size for win32-eventlog > (was infiniteloop bug...)

Hi all, I''ve released 0.2.2 of win32-eventlog. There was a rather nasty bug in the read() method I hadn''t noticed before - it wasn''t reading all the records! In addition, this package officially requires Ruby 1.8.0 or later, as I have replaced the STR2CSTR() functions with StringValuePtr(). Let me know if you find any bugs. Thanks. Dan

Hi all, A user recently ran into an issue with win32-eventlog and the EventLog#read method when reading a saved log file. It seems that there''s an issue. After some experimentation I found that the problem seems to be that the initial buffer to ReadEventLog() in line 558 is too small, so it tries a second call to ReadEventLog() with a larger buffer. The problem is that, after I

Hi all, Tim Uckun reported, and I''ve confirmed, that you can''t write to the Windows PowerShell event source for some reason. Tim thought it might be because of the space in the name, but my attempt to quote it did not seem to help. In order to follow along, install PowerShell, create the foo.dll using the foo.mc file in the ''test'' directory, and try the

> -----Original Message----- > From: Joey Gibson [mailto:joey@joeygibson.com] > Sent: Monday, October 18, 2004 10:07 AM > To: Berger, Daniel > Cc: win32utils-devel@rubyforge.org > Subject: Re: Another Interesting "Problem" with Win32-EventLog > > > Berger, Daniel wrote: > > > I cannot duplicate this on my Windows XP Pro box here at work. > >

That''s weird. Line 296 is just a call to FormatMessage(). Folks on the mailing list - could this be a wide character issue? Buffer too small maybe? Regards, Dan Pe?a wrote: > forgot: > > it segfaults on the win2k3 server (domain controller). > > it has _not_ segfault on my winxp pro though. > > > > # -----Original Message----- > # From: Pe?a, Botp

Pe?a wrote: > # Ok, fixed and released as 0.4.1. Thanks for the report! > > Hi Dan, > > the new change_notify does not exhibit the resource error anymore. > BUT it skips (and does not log) some records. > > Tail is much better and does not skip. > > kind regards -botp > NotifyChangeEventLog() only checks every five seconds, max, iirc. If an app logs more

Pe?a wrote: > Hi Dan, > i get a segfault on windows-pr if i run mulitple tails by threading, one thread for each host i''m tailing. > > C:\family\ruby\win-eventlog>dtail.rb > thread/tail-ing Security on host1 > thread/tail-ing Security on host2 > thread/tail-ing Security on host3 > thread/tail-ing Security on host4 > thread/tail-ing Security on host5 >

Bugs item #28904, was opened at 2011-02-02 18:41 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=28904&group_id=85 Category: win32-eventlog Group: Code Status: Open Resolution: None Priority: 3 Submitted By: Jason Bourne (jbourne) Assigned to: Nobody (None) Summary: Gem win32-eventlog v0.5.2 on Ruby 1.9.1 and 1.9.2 Initial Comment: 1.Requirement:

Hi all, I''m working on the EventLog#read method for the pure Ruby version of win32-eventlog, but I''m stuck on the get_description private method. Here are the problems: * I don''t think I''m advancing the EVENTLOGRECORD properly between iterations. Take a look at the end of the "while dwread > 0" loop. I get some records, but not all of them.

> -----Original Message----- > From: Joey Gibson [mailto:joey@joeygibson.com] > Sent: Monday, October 18, 2004 9:29 AM > To: Ruby-Talk; Berger, Daniel > Subject: Another Interesting "Problem" with Win32-EventLog > > > After Daniel patched the Win32-EventLog code to properly handle > "strange" event messages (I''ll leave it to Daniel to

> -----Original Message----- > From: Joey Gibson [mailto:joey@joeygibson.com] > Sent: Tuesday, October 19, 2004 6:11 AM > To: ruby-talk@ruby-lang.org; Berger, Daniel > Subject: Re: Another Interesting "Problem" with Win32-EventLog > > > Daniel Berger wrote: > > >After getting home from work today I tried again on my home machine. > >My

Hi again, Pe?a wrote: > # > i get a segfault on windows-pr if i run mulitple tails by > # threading, one thread for each host i''m tailing. > > argh, this is getting tricky. i''m getting empty records and weird characters too :) > > -------- > record_number : 20983290 > time_generated : Tue May 30 16:15:27 China Standard Time 2006 > time_written :

Hi, Hm, the string inserts are different, too. Any encoding issues? Your user name uses extended ASCII, too, right? Not sure if that''s significant or not. I''ve cc''d the win32utils-devel list to see if anyone has any ideas. Thanks, Dan botp wrote: > On 12/4/07, Daniel Berger <djberg96 at gmail.com> wrote: >> Can you tell us which record numbers in

Hi all, I know that once upon a time I said that we shouldn''t use DONT_RESOLVE_DLL_REFERENCES (line 698), but it appears that this was wrong headed thinking for win32-eventlog. A couple of folks have complained that they couldn''t get descriptions for event records in some cases, and I have a strong feeling that''s the culprit. Can anyone see a downside to using

All, I got a bug report from Greg Holmes where the description wasn''t being returned properly. At the moment, if there''s no event associated with the event id, then the description is empty. However, it turns out that there can still be associated information about the event. So, I propose the following tweak to the get_description private method: # If FormatMessage()

I think I''ve narrowed it down to this call in eventlog.h hModule = LoadLibraryEx( szExeFilePath, 0, DONT_RESOLVE_DLL_REFERENCES ); In all cases where the description is returning nil instead of actual text, this appears to be the culprit. I''ll do some more research. In the meantime, ideas welcome. :) Dan

> -----Original Message----- > From: win32utils-devel-bounces at rubyforge.org > [mailto:win32utils-devel-bounces at rubyforge.org] On Behalf Of > Heesob Park > Sent: Tuesday, May 16, 2006 9:51 PM > To: Development and ideas for win32utils projects > Subject: Re: [Win32utils-devel] Need a little help with the > pure Rubywin32-eventlog > > > Hi, > >