Hi Stefan, Pendl Stefan wrote: > Imagine following situation: > Installation will last for 5 minutes usually, there is no timeout specified > explicitly. > Now this installation hangs for one hour, since there is no timeout specified > in the package.
Why should it "hang" for 1 hour then? As Tomasz already explained there are two types of timeouts: - A timeout per COMMAND. This timeout is set to 3600 seconds per default (1 hour). WPKG (the server-side js script) will terminate the command if it does not finish its job before the timeout is reached. - A timeout for the whole WPKG service run time. WPKG client terminates wpkg.js if it runs for longer than this amount of time. BUT: Remember that if a command terminates after 1 sec for instance, then wpkg.js will return immediately and also the service terminates immediately after wpkg.js finished its job. So if all your installations are running properly and finish within 30 seconds, then WPKG client will run no longer than 30 seconds - even if you set the timeout to 1 hour. So set the timeout as high as possible to complete the longest operation expected. The timeout is mainly there in order to prevent WPKG (client or server-side) to block the machine too long in case something goes wrong (e.g. installer asking for user input and does not terminate/finish therefore. br, Rainer ------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
