[wpkg-users] [Bug 86] Ability to postpone reboot to the end of the script execution.

[bugzilla-daemon at bugzilla.wpkg.org]

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





--- Comment #1 from Rainer Meier <skybeam at users.sourceforge.net>  2007-12-03 22:50:41 ---
Created an attachment (id=76)
 --> (http://bugzilla.wpkg.org/attachment.cgi?id=76)
Added postpone feature.

After some tests I am proud to announce a new testing-release of WPKG.

It now supports the following reboot flags on package level:
reboot="true"
reboot="false"
reboot="postponed"

and the following reboot flags on command level:
reboot="true"
reboot="false"
reboot="delayed"
reboot="postponed"

This is a slightly different implementation than discussed on the mailing list
before but I think it makes it easier to handle. The idea is that simply
package-level and command-level reboot flags might schedule a reboot on certain
timeline points:

immediate (1) => package (2) => postponed (3) => none

(1) can be specified on reboot=true on command-level
(2) can be specified with reboot=true on package level or reboot=delayed on
command-level
(3) can be specified with reboot=postponed either on command or on package
level


I hope everybody is fine with that...

Here's a change log:

Changes 2007-11-24, v1.0-RC2 by Rainer Meier <skybeam (at)
users.sourceforge.net>
NEW: Allows "true", "false" and "postponed" as a value of the reboot attribute
         within the package node. The states have the following effect:
         "true"      Immediate reboot after package installation.
                     This will take precedence of any command-level
reboot="postpone"
                     attribute if present and reboot immediately after package
                     installation.
                     A reboot="true" attribute on command-level will still
result in
                     an immediate reboot.
                     Resulting status depending on command-level reboot flag:
                     "true"      immediate reboot after command execution
                     "delayed"   reboot after package installation
                     "postponed" reboot after package installation
                     "false"     reboot after package installation
         "postponed" Schedule reboot after installing all packages within this
                     session, for example after synchronizing. 
                     Resulting status depending on command-level reboot flag:
                     "true"      immediate reboot after command execution
                     "delayed"   reboot after package installation
                     "postponed" reboot after all actions are completed
                     "false"     reboot after all actions are completed
         "false"     No reboot unless one is defined at command-level.
         or not set  Resulting status depending on command-level reboot flag:
                     "true"      immediate reboot after command execution
                     "delayed"   reboot after package installation
                     "postponed" reboot after all actions are completed
                     "false"     no reboot

         As a result there are four possibilities to schedule a reboot in order
of
         precedence:
         immediate   Command node specified reboot=true, immediate reboot takes
place.
         package     Reboot is issued right after installing:
                     - package specifies reboot="true"
                       OR
                     - any command node specified reboot="delayed"
         postponed   Reboot will take place after all packages have been
applied.
                     - package specifies reboot="postponed"
                       OR
                     - any command node specified reboot="postponed"
         none        No reboot is issued by this package:
                     - package does not specify reboot or specifies
reboot="false"
                       AND
                     - no command node specified any form of reboot reboot

         This means that an immediate reboot always has the highest priority.
You
         can just set "reboot markers" on a "timeline" on package and command
level
         where the closest reboot marker will be executed:
         immediate => package => postponed => none

MOD: Exit code 0 is not any more automatically regarded as "successful" value.
     Even code 0 is now evaluated by exit code nodes. If no node is found it is
     still assumed that the command was successful. This allows administrators
     to schedule a reboot (immediate/delayed/postponed) even on exit code 0.


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







Easy Software Deployment >> http://wpkg.org
_______________________________________________
wpkg-users mailing list
wpkg-users at lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users