[wpkg-users] [Bug 132] wpkg.js should return 3010 even when reboot is overridden

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=132





--- Comment #5 from Rainer Meier <r.meier at wpkg.org>  2009-03-29 16:09:13 ---
OK, actually I re-implemented this change. Now WPKG behaves slightly different.
Mainly it does not exit with code 3010 any more when reboot is overridden
because this could make WPKG client to actually initiate a reboot while it
should be actually omitted.

Now WPKG exits with a special code. If you still want to exit with code 3010
this possibility still exists.

Relevant changes:
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.


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.