2011/1/7 LAPLAUD François <lapl...@sdis72.fr>: > Yes indeed, > Here are my needs : > - a working wpkg ( ;-) )
I would start with this. Just follow the wiki http://wpkg.org/WPKG_QUICK_INSTALL guide. > - possibility to run wpkg periodically to be able to deploy packages in > background while users are working. For my part, I won't force shutdown, but > when I need it, I will add an install cmd in my packages using msg.exe > telling the user to Reboot when he can to complete an update. (to run it > periodically I thought about scheduled tasks. If I need to use scheduled > tasks, why would I run a service wich will in return run a script whereas I > can run that script directly ? in both cases I will have to create a scheduled task...) No, if you have a service you do not need to create a scheduled job. That's the point of running a service, it runs automatically after booting. You can create a job to run at boot time, but that is not a service. You can have both. While I can understand you do not want to have both, it will be easier for you to have both. Bootstrap the client installation so you know it's working, then install scheduled jobs with it to run it periodically. This is redundancy, it can never hurt. We run our wpkg and our cfengine frameworks like this. Besides, the wpkgservice is not a typical one. It does not reread its config continually. it just runs after boot and then sits there doing nothing. It will not consume any significant resources. > - when the scheduled tasked is about to run wpkg, I would like it to wait for > some random time between 1 and 30 minutes for instance so that the network is > not overloaded. (I suppose this part will need little modifications of the > wpkg.js script itself but seems to be a quite easy one) If you run it as a service you do not need to worry about this. Not everybody turns their pc on at the same time. In the time we have been running this, I have not seen significant problems even with large packages (well, we do have fast networks, that helps too). We are not deploying it to wan offices with slow links. If you have slow wan links, then this could indeed be a problem with large software packages. What I like about wpkg is that it runs quite fast, so usually everything is done while the user is getting some coffee after turning their pc on. With our new workstations you really need to know something is being installed because they are so fast that I usually have to check the event log to see any activity, it's done before I know it. -- natxo ------------------------------------------------------------------------- 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