There's an API function to get the oldest event record in an open EventLog.
However, I don't see anything that allows me to immediately jump to the
end of the EventLog so that I can wait for notifications of new events.
Is it more appropriate to position to the oldest event and then read
forwards until the end of the log is reached, following by waiting on an
event notification that signals the arrival of a new event in the EventLog?
Or, is it better to explicitly read the oldest event and then read
backwards sequentially by 1 record?
The reason that I ask.... I'm not interested in existing events in the
EventLog [only new ones that arrive after I'm running], I don't want to
programmatically clear the EventLog as the administrator might need the
contents, and the EventLog might be configured to overwrite itself as a
ring-buffer so the lowest # event record might not actually be the oldest
event in the EventLog. I simply need to spin past all events to the current
end of the EventLog and then wait for new events. If the EventLog is large,
I'd rather position directly to the end rather than incurring the overhead
of reading every single record.
ChuckChopp (at) rtfmcsi (dot) com http://www.yqcomputer.com/
RTFM Consulting Services Inc. 864 801 2795 voice & voicemail
103 Autumn Hill Road 864 801 2774 fax
Greer, SC 29651
"Racing to save lives"
The Leukemia & Lymphoma Society - Team in Training
Do not send me unsolicited commercial email.