<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000'>Hi Antony,<div><br></div><div>Ideally you will want to run WPKG at startup (or shutdown) so there's no chance that a program will be in use. </div><div><br></div><div>Typically an installer can handle the fact that the program it's updating is running, so most people will just let that install fail rather than kill the running program and potentially lose data.</div><div><br></div><div>However most of the time you see taskkill being used is where you need to ensure that a separate application isn't running - eg Flash & Java won't install correctly if Firefox is running - hence you end up with an inconsistent installation state where WPKG thinks that Flash is correctly installed, but the plugin didn't get added to Firefox. To avoid this we run Taskkill on Firefox before installing Flash, to ensure Firefox isn't running so the plugin can be added.</div><div><br></div><div>It's a trade off between ensuring a clean install and annoying a user by having a program quit for no apparent reason. </div><div><br></div><div>That said, don't run WPKG when users are logged on or you will have many other issues - for example; what happens when somebody tries to run a program that is being updated? Run it at startup or shutdown.</div><div><br></div><div>Cheers Jon<br><br><div><span name="x"></span>-- <br>Jon Rhoades<br>Research Information Systems<br>Eastern Hill Academic Centre<br>(Incorporating The University of Melbourne Departments of Medicine, Surgery and Clinical School (St.Vincent's), St Vincent's Institute and O'Brien Institute)<br><br>St Vincent's Institute<br>9 Princes St Fitzroy Vic 3065<br>p: 03 9288 2480 | x: 2399 | f: 03 9416 2676<br><br>www.stv.unimelb.edu.au<br>www.svi.edu.au<link rel="stylesheet" type="text/css" media="screen" href="chrome-extension://fcdjadjbdihbaodagojiomdljhjhjfho/css/atd.css"><span name="x"></span><br></div><hr id="zwchr"><b>From: </b>"Antony Awaida" <antony@bizappcenter.com><br><b>To: </b>wpkg-users@lists.wpkg.org<br><b>Sent: </b>Thursday, 18 July, 2013 1:12:04 PM<br><b>Subject: </b>[wpkg-users] Updating packages without disrupting end users<br><br>Hi Folks:<br><br>Several of the silent installers in the WPKG database use taskkill<br>when updating from one version of a package to a newer version (e.g.<br>Firefox).<br><br>From an end user perspective, this means that I could be using an<br>application or a browser and my application will be terminated with no<br>notification and I will lose all my work.<br><br>Is there a good way to deal with this?<br><br>Thanks,<br>Antony<br>-------------------------------------------------------------------------<br>wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/<br>_______________________________________________<br>wpkg-users mailing list<br>wpkg-users@lists.wpkg.org<br>http://lists.wpkg.org/mailman/listinfo/wpkg-users<br></div></div></body></html>