[wpkg-users] wpkg can fill-up event log and then stops

[Tomasz Chmielewski]

Urs Rau schrieb:
> Wondering if any of you have found out as well, that wpkg can fill-up
> the event log rather quickly, if it is processing a lot of installs and
> re-runs frequently, or if you write install scripts or batch files that
> are too "chatty".

Yes, I noticed that, too.
Windows has ridiculously small maximum log size set by default - 512 kB, 
or something near.
One can easily fill it, and then, some of the applications that write to 
the Event Log will malfunction. One of such apps is our wpkg.js, 
unfortunately.


> The "odd" thing I noticed is, that as and when the event log is full and
> it can't overwrite the events yet, because the default 7 days haven't
> been reached, then wpkg appears to be stopping to work and apply the
> packages.
> 
> The only way to get it going again, appears to be to clear the event log
> on the affected machines. But this isn't a good state of affairs. Does
> anybody have a script handy that changes the defaults for the event log
> to be to 'overwrite' 'as needed' and not as is 'default' only after the
> entires to be overwritten are 7 days or older.

Perhaps instead of clearing the Event Log it would be wiser for wpkg.js 
to continue, even if it can't write to the Event Log.
After all, WPKG is not some security application which should lock up 
when it can't log the events (actually, you can set up Windows in a way 
that it bluescreens when Event Log is full).

I'll take a look at it.
See also here:
http://wpkg.org/FAQ#I.27m_getting_an_error_.22Event_log_file_is_full.22.2C_and_then_WPKG_exits


-- 
Tomasz Chmielewski
http://wpkg.org


wpkg-users mailing list
wpkg-users at lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users