Brian May schrieb:
> Brian May wrote:
>> It seems to work.
>>
>> Can I please confirm why you use "start"? Is this for extra debugging?
>
> Looks like a race condition exists, due to using start. The process is
> started for upgrading wpkg, and at the same time wpkg continues and
> checks the latest version is already installed - but it isn't installed
> yet because the background task is still executing.
And that check will fail, as file version will not match yet.
The check will succeed on the next WPKG startup though.
This is intended.
> Probably better just to call the batch file directly.
I think killing WPKGSrv.exe will also kill its child processes:
- cscript ...\wpkg.js
\- any other child of cscript
So I'm afraid that if we don't use "start" to start the script in
background, taskkill would also kill our batch script, and prevent WPKG
Client from upgrading?
Also, when using that approach, I think it is good to add:
ping -n 120 127.0.0.1 >nul
to make sure WPKG doesn't continue while it's killed...
--
Tomasz Chmielewski
http://wpkg.org
|
|