Sorry, but i'm a bit missed in this thread. 1) to upgrade wpkg client, the service have to be stopped; because the service run wpkg.js that run the install batch script, we cannot kill the service without 'start' or we will kill ourself. Relatively easy.
2) but if we have 'delayed logon' feature in use, we cannot use the trick to kill it, because a component (a dll) are directly executed by NETLOGON, that cannot be killed. A question (but i'm a unix guy): for me it is normal to upgrade binary in execution, simply the newer version will be available next time we reboot the machine. Asked in another way: why not rewrite the installer so it handle all this stuff, upgrade the binary and then force 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) ------------------------------------------------------------------------- Reporting bugs, all WPKG mailing lists >> http://wpkg.org/Support _______________________________________________ wpkg-users mailing list [email protected] http://lists.wpkg.org/mailman/listinfo/wpkg-users
