http://bugzilla.wpkg.org/show_bug.cgi?id=275
Summary: Bullet-proofing log files.
Product: WPKG
Version: other
Platform: PC
OS/Version: All
Status: NEW
Severity: trivial
Priority: P2
Component: wpkg.js
AssignedTo: man...@wpkg.org
ReportedBy: k.e.jo...@brighton.ac.uk
QAContact: wpkg-users@lists.wpkg.org
WPKG makes a great job of handling log file output but some days people do
stupid things and can kill it quite easily ;-)
I added a package that installed updated network drivers. As you can imagine,
at some point during their installation the network was dropped and when WPKG
tried to write to the logfile that I'd redirected to a server share it just
crashed and burned.
The error wasn't bubbled through to error handlers so I'm guessing I need to
dig a bit further. In the interrim, might I suggest that logfile writes get
wrapped with a try/catch just in case something happens out of the normal
context of wpkg's actions and error reporting model?
As Confuscious says, **** happens life goes on... and so should WPKG :-)
Keith
--
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
