>
> >>
> >> Thanks heaps, I will look into that tomorrow :)
> >>
> >> Jacob Jarick wrote:
> >> > Thanks Tomasz,
> >> > the delay brings up the gui :)
> >> >
> >> > Unfortunately it seems to delay login by 1 minute everytime
> >> after that even if there are no packages to be installed.
> >> > Is there a way around this or is it a current limitation ?
> >>
> >> It shouldn't be the case.
> >> If the delay is enabled and wpkg.js has really nothing to do,
> >> you should
> >> see this dialog for 10 seconds or so (the time when wpkg.js starts,
> >> reads config files, makes check and eventually quits).
> >>
> >> If the delay is longer for you, this might suggest that wpkg.js is
> >> really doing something (hangs at installing something etc.).
> >>
> >
> > I am using the latest beta version of the WPKG client and
> run it at shutdown.
> > This way I do not have users waiting till WPKG is finished
> or any running process conflicting with WPKG.
> > In addition a reboot is never needed, since the
> installation is done just before it.
> >
> > ---
> > Stefan
>
> Hi Stefan,
>
> When you run WPKG at shutdown how to you prevent Windows from
> killing your processes ?
>
> Thanks
> Paul
>
Paul,
the WPKG client service is set to add a pre-shutdown delay, which you specify in the client GUI, like the logon delay.
This is the maximum timeout after which the wpkg.js will be killed.
I do have some installations lasting between 30 and 45 minutes, so I set the shutdown delay to the maximum possible, which is 90 minutes.
This way a big installation and some small ones can successfully finish, till the machine finally shuts down.
I have included a timeout for the commands of these installations too, to avoid waiting the whole 90 minutes in case of a failure.
See the Wiki for the possible timeout definitions.
---
Stefan
|
|