Hey Greg What do you think about creating an sheduled task, which runs by example every 12 hours. So you can start the command "cscript <path to wpkg.js>\wpkg.js /synchronize /quiet" spaced On a machine, which will never be rebooted...
-----Ursprüngliche Nachricht----- Von: wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users-boun...@lists.wpkg.org] Im Auftrag von Gregory Orange Gesendet: Montag, 22. Februar 2010 07:54 An: wpkg Betreff: [wpkg-users] why leave client service running? Hi everyone, I've just picked up Wpkg again after not really getting it going a few years ago. I'm impressed by how easy it has been to install and get off the ground. Thank you for such a great project, helping to fill in one of Windows' biggest gaps: package management. I'm grateful also for the pre-built client, such that I don't have to think about rolling my own deployment, and the GUI is good for generating settings for the first time. My question: What is the point in _not_ ticking "Stop the service when all actions are done"? Why would I want the service running if I set the execution mode to be at system startup? On a related note, what happens with computers that are never rebooted or shut down? Is there some recommended way of getting their package status synchronised? Cheers, Greg. ------------------------------------------------------------------------- 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 ------------------------------------------------------------------------- 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
