search for: eventlog_forwards_read

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

...see is something like this: * Set a @last instance variable in the constructor. * In the read_last_record function, check to see if @last is nil. If it is nil, then it''s our first read. Use the current approach, and set @last to the record number. * If @last isn''t nil, use EVENTLOG_FORWARDS_READ | EVENTLOG_SEEK_READ flags instead, and use @last + 1 as the offset. I tested this in the pure Ruby version and it seems to work fine. Sound good? Dan

...f the network interfaces may not get the protection as desired by the applied IPSec filters. Please run IPSec monitor snap-in to further diagnose the problem .\r\n\r\n\r\n"> UGH. So, what''s the solution? Just start at the offset returned by GetNumberOfEventLogRecords() and use EVENTLOG_FORWARDS_READ | EVENTLOG_SEEK_READ instead? Was it always like this and no one noticed? Did I goof a commit somewhere? Or are things actually working and I''m panicked for no reason? Dan