[wpkg-users] Global max execution time hardcoded?

[Rainer Meier]

Hi Marco,

On 26.03.2013 11:30, Marco Gaiarin wrote:
> Yes, probably it is caused by my bad WPKG experience and
> ''programming'', but i cannot sustain a 60 minutes delay on boot, and
> now i've no time to recheck all my recipes to value and set timeout.

I think we are perhaps talking about different timeouts. The WPKG timeout is 
only about timing out single commands. So even if you set it to ridiculously low 
value like 1 minute, then despite the fact that it might mark most package 
installations as failed due to timeout on commands WPKG might still run for more 
than 1 hour if many commands are run.

Sorry but I really don't think you should abuse single-command execution time 
limit to limit execution time of WPKG itself.

As you confirmed you're looking forward to terminate WPKG execution after a 
specific maximum WPKG run time. This timeout however is not controlled by WPKG. 
WPKG will just try to finish its complete job. If this takes too long for you 
then you should ask for a change request on the instance running WPKG (WPKG 
client, WPKG-GP etc.). So if WPKG takes too long (no matter if it's due to 
single command taking too long or due to the fact that just many software 
packages are applied) a client might terminate WPKG and let users start to work. 
However this might leave the client in inconsistent state. Imagine Office 
installation. I recently installed Office 2010 via WPKG and some clients took 
about 45 minutes on the uninstall command of Office 2007 and 10 minutes on the 
installation of Office 2010. If you terminate WPKG in the middle then you will 
be left with no working office installation at all.

As far as I remember WPKG client offered a logon dely feature on Windows XP 
which also allowed to skip the delay (not sure though as I never used this 
feature). WPKG-GP might technically be unable to offer WPKG run on user input 
(e.g. pressing key combination to terminate WPKG). But WPKG-GP might introduce a 
global timeout and after timeout let users logon as normal either keeping WPKG 
run in background or terminate it.

br,
Rainer