eventlog tests and writing/clearing the logs

[Paul Vriens-2]

Hi,

I'm mostly done with the parameter tests and I'm starting to look what
functional tests I can add.

The biggest issues I have are:

- Writing events needs to go a registered event source
- Clearing an eventlog has to be with a registered event source
- Registering our own event source can be done but needs a reboot to
clear out any remnants.

As we really want to test all of this, my proposal is to run these tests
only in interactive mode. Doing so at least gives us some confidence
that people know what they are doing.

Worst case, they will have an extra event source that can only be
deleted by removing some registry entries, a reboot and removal of the
actual eventlog file (the registry removal will be part of the cleanup
of course but you never know).

Any thoughts on this? Correct approach?

--
Cheers,

Paul.

[Nikolay Sivov]

On Mon, Nov 2, 2009 at 7:35 PM, Paul Vriens <paul.vriens.wine@...> wrote:
>
> Any thoughts on this? Correct approach?
>

Do you plan to implement a real logging or what all of this is for?

> --
> Cheers,
>
> Paul.
>

[Paul Vriens-2]

On 11/02/2009 05:39 PM, Nikolay Sivov wrote:
> On Mon, Nov 2, 2009 at 7:35 PM, Paul Vriens<paul.vriens.wine@...>  wrote:
>>
>> Any thoughts on this? Correct approach?
>>
>
> Do you plan to implement a real logging or what all of this is for?

If you mean, get functional event logging into Wine, the answer is yes.

--
Cheers,

Paul.

[Paul Vriens-2]

On 11/02/2009 05:51 PM, mellery wrote:
> Hi,
>
> Will this involve implementing advapi:RegisterTraceGuidsW, and can I
> help at all?
>
> Thanks,
> Mike

Event tracing is totally different from event logging. Be my guest to
pick that up ;)

Maybe it's a good idea to split the advapi32/eventlog.c into eventlog.c
and eventtrace.c once the tracing is fleshed out a bit more.
Particularly if we move most of functionality to services.exe (as on
Windows).

--
Cheers,

Paul.