http://bugzilla.wpkg.org/show_bug.cgi?id=109 Rainer Meier <r.meier at wpkg.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Rainer Meier <r.meier at wpkg.org> 2008-04-21 23:41:43 --- I agree that it can be a dangerous thing. But this is nothing we can change. What we can do is actually making sure that WPKG even works if the log is full. So here is what I implemented now: In case the event log is full (or any other exception is thrown during write attempt) event log writing is disabled completely for this session. Additionally the message caused the error is printed to STDOUT in order not to get lost. All following messages are printed to STDOUT (no further attempt to write to event log during this WPKG execution). Writing to log-files is not affected by this change. There will be just one additional ERROR severity entry which indicates event log failure. I am releasing updates soon - after testing :-) -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |