similar to: EventLog#tail followup

Bugs item #4598, was opened at 2006-05-29 11:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=4598&group_id=85 Category: win32-eventlog Group: None Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: possible wrong condition Initial Comment: Is this condition right? (eventlog.rb, line 494

I just discovered something awful. The EventLog#tail method does not work the way I thought it did. Instead of picking up new events as they''re added, it''s really just iterating backwards through the current event log backwards. Look at this sample below. The first record is correct. Then another event happens, but instead of the latest record, I get an *earlier*

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

Hello, I run a Windows domain based on Samba 3 and I am searching for a way to distribute/deploy software to clients. I.e., a user logging on to a client, software should be automatically installed or upgraded. Is there any common solution? I heard of MSI packages, but I don't know if it is necessary to create MSI packages of all installations... Thanks Florian

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

Hi all, Ok, I''m getting closer on this get_description failure and the mscoree.dll file. It has something to do with the way we''re calling FormatMessage(). Consider the following C code, which behaves exactly the same way as the current Ruby code: #include <windows.h> #include <stdio.h> int main(){ HMODULE hmod; int rv; char buf[4096]; char* dll

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

Note to anyone paying attention - this was solved off list. Apparently I just goofed the patch. Dan > -----Original Message----- > From: win32utils-devel-bounces at rubyforge.org > [mailto:win32utils-devel-bounces at rubyforge.org] On Behalf Of > Daniel Berger > Sent: Wednesday, May 17, 2006 10:24 PM > To: Development and ideas for win32utils projects > Subject: Re:

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

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...)

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

Hi all, I''ve almost got win32-eventlog 0.3.0 ready to go. There are some minor tweaks to the API, but everything is still backwards compatable. But, what I really want to discuss is setting up a default event source for Ruby. Here''s what I''m thinking - offer the option of installing a "RubyMsg" event source when you install win32-eventlog. The name

> -----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: 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. > >

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

Give it a shot, lemme know how it goes. Dan

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:

https://bugzilla.mindrot.org/show_bug.cgi?id=752 kevin.m.smyth+mindrot at gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kevin.m.smyth+mindrot at gmail | |.com --- Comment #4 from

<rant> So, we've got a couple of WinDoze servers, and we getting logs from them. Except the logs seem to stop on occasion. My manager set me onto this (I *loathe* WinDoze, but someone's gotta do it), and I finally found out that a previous co-worker installed eventlog-to-syslog, which seems to be hosted in google code. And it *seems* to have come from Purdue Univ. So < found the