Mandi! Tomasz Chmielewski In chel di` si favelave... > Read the source, Luke ;) > Look for "Returns the package reboot attribute value". ...that is more or less what on: http://bugzilla.wpkg.org/show_bug.cgi?id=86 The source say me: * "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 So if i set on package level reboot=false and on command level reboot=postponed (as i do), after all wpkg.js actions a reboot will be scheduled, as i supposed. What i'm saying is that if, as a logged user, i run wpkg,js 'manually' or restart the WPKGClient service, reboot are logged on event log and take place effectively. But if i simply leave the WPKGClient to upgrade itself at boot time (eg, with wpkglogon), the reboot are logged on event log but not take place (and no error at all). This is not a real trouble (the new wpkg will be available at next bootup), and i've not tried to determine if this is a trouble for the wpkg update only or for every update done on bootup that need a reboot. -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia'' http://www.sv.lnf.it/ Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN) marco.gaiarin(at)sv.lnf.it tel +39-0434-842711 fax +39-0434-842797 Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA! http://www.lanostrafamiglia.it/chi_siamo/5xmille.php (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA) |