[wpkg-users] frequency of wpkgservice checking for new installs

Brad Langhorst brad at coopmetrics.coop
Wed Jun 13 18:55:47 CEST 2007


On Wed, 2007-06-13 at 11:51 +0200, Falko Trojahn wrote:
> > Mandi! Tomasz Chmielewski
> >   In chel di` si favelave...
> >
> >> There is one slight problem with that: WPKG Client and wpkg.js are not
> >> very well integrated (it will change slowly in the future; right now,
> >> there are even problems with restarts initiated by wpkg.js etc.).
> >> This means, we would have to learn WPKG Client to read and parse files
> >> used by wpkg.js. Which means - parsing profiles.xml is not enough, and
> >> profiles can be also kept in "profiles" directory.
> >
> > A note: this is a very good point about wpkg: if client are smaller,
> > and totally indipendent from the server, and all of the core 'code' are
> > server side, there's little or no possibility to break something.
> >
> > So, i clearly interesting in new featue, but please don't break this
> > simple and robust approach.
> >
> >
> > In this topic: why not writing a recipe/package that simply add a
> > task (with schtasks) that run wpkg as a regular basis?
> Ack. Just a
>  net stop "windows packager"
>  net start "windows packager"
> (or "wpkg service") would do it, too.
The feature i'm thinking about would be be able to use the groupings set
up in profiles.xml to do management (eg: update all 150 lab machines
every 12 hours).

I think being able to use those groupings is better than having to
create ad-hoc groups. 

brad
-- 
Brad Langhorst
CTO - CoopMetrics




wpkg-users mailing list
wpkg-users at lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users



More information about the wpkg-users mailing list