search for: eventlog_seek_read

Displaying 3 results from an estimated 3 matches for "eventlog_seek_read".

2006 May 29
3
[ win32utils-Bugs-4598 ] possible wrong condition
...etail&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 if flags | EVENTLOG_SEEK_READ > 0 offset = buf[8,4].unpack(''L'').first + 1 end To me it seems that it is always true as E_S_R == 2. Maybe this is how it was meant: unless flags & EVENTLOG_SEEK_READ > 0 I haven''t understood the rest of the code, so I''m not sure ab...
2006 May 20
1
EventLog#tail followup
...is: * 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
2006 May 20
0
EventLog#tail is broken
...ay 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