[wpkg-users] [Bug 132] wpkg.js should return 3010 even when reboot is overridden
bugzilla-daemon at bugzilla.wpkg.org
bugzilla-daemon at bugzilla.wpkg.org
Sun Mar 29 16:10:28 CEST 2009
http://bugzilla.wpkg.org/show_bug.cgi?id=132
Rainer Meier <r.meier at wpkg.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #121 is|0 |1
obsolete| |
--- Comment #6 from Rainer Meier <r.meier at wpkg.org> 2009-03-29 16:10:25 ---
Created an attachment (id=128)
--> (http://bugzilla.wpkg.org/attachment.cgi?id=128)
New WPKG release with some fixes and improvements.
Changes in this release:
FIX: In case a command is executed which does not exist (WScript.Shell.exec()
throws exception) WPKG does not immediately terminate.
FIX: In case a command is executed which does not exist (WScript.Shell.exec()
throws exception) WPKG does not immediately terminate.
FIX: Removed unnecessary check for undefined checks in getPackageChecks()
method. It seems that selectNodes(String) never returns null but instead
returns empty collection.
FIX: Updated help and config.xml with grammar and consistency fixes as proposed
by Jens Geile. Thanks Jens. Fixes Bug 116.
FIX: If a reboot is initiated but overridden WPKG was returning exit code 0.
This behavior has been changed to return code 3010 in this case which
allows external tools to detect that a reboot should be executed.
Fixes Bug 132.
MOD: Changed behavior of wpkg.js again in case reboot is overridden.
Previously it was exiting with exit code 3010 but this caused WPKG client
to initiate a reboot immediately after wpkg.js terminated.
Now WPKG returns code 3010 << 8 (3010 bit-shifted by 8 bits to the left)
which evaluates to a decimal value of 770560. This allows an external
tool to verify if a reboot was initiated but overridden.
If you would like WPKG to exit with code 3010 without issuing a reboot
consider to specify a reboot command within the configuration
(see rebootCmd in config.xml or /rebootcmd: switch) which points to a
script which does not do anything. In this case WPKG executes the script
(e.g. reboot.cmd) and then exits with code 3010.
This was discussed in Bug 132.
NEW: Shows usage if executed without parameter (instead of just throwing an
error and exiting).
MOD: Improved documentation.
--
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the wpkg-users
mailing list