[wpkg-users] wpkg software deployment using bittorrent

[Peter Gough]

I know there are other considerations and it's not something I do in my
environment but would running this as a scheduled task rather than at
startup/shutdown remove this as an issue?


On 12 July 2013 10:07, Rob Bos <rbos-wpkg at novylen.net> wrote:

> On 13-07-11 05:01 PM, Carlos R. Pasqualini wrote:
>
>> uhh, wpkg running for 10 minutes, and i am using wpkg-gp on startup...
>> with a screen locked out saying 'wpkg is installing xyz...' not viable
>> at all!!!
>>
>> i was thinking about scheduling a task on login event, but that would be
>> a thing to think about, we should need to take into account the user's
>> privileges to launch the seeder and access de LOCALCACHEPATH
>> i think we need to think more about this...
>>
>
> There's also the general fact that a package big enough to be worth
> torrenting may also take 5-10 minutes to install, so the backgrounded seed
> might end before the package even finishes installing. That's the case for
> a few programs, like Creative Suite; the installation finishes well after
> the seed is done.
>
> Eliminating the seed phase entirely or reducing it wouldn't be a big deal,
> it'd just mean that peering would only happen during download.
>
> Lots of different options.
>
> I'm planning on actually spinning up seeds as a startup script separate
> from WPKG - you'll notice toward the end of torrent.cmd that it saves the
> torrent and destination to a file; the plan is to have another script use
> that to spin up local seeds on startup during imaging, but not during
> normal operations. (our startup scripts distinguishes between 'setup' and
> 'startup' operation modes)
>
>
>
>>  i haven't found any cleanup process of the local save path. how do you
>>>> manage old installers removal? may be adding a delete subroutine in
>>>> the :seed section, but we need to check if the program has been
>>>> installed correctly too, or may be launch the cleanup on the next
>>>> version of this package... just guessing
>>>>
>>> As above, stick the deletion into the WPKG package so you can do it as
>>> appropriate for the package. Some require the media to be kept around
>>> for uninstall.
>>>
>>
>> Thanks for your tips Rob!
>>
>> when i come with an implementation, i will document it and provide here
>> if you get some ideas you can implement.
>>
>> best regards
>>
>>
>> Charly
>>
>>
> ------------------------------**------------------------------**
> -------------
> wpkg-users mailing list archives >> http://lists.wpkg.org/**
> pipermail/wpkg-users/ <http://lists.wpkg.org/pipermail/wpkg-users/>
> ______________________________**_________________
> wpkg-users mailing list
> wpkg-users at lists.wpkg.org
> http://lists.wpkg.org/mailman/**listinfo/wpkg-users<http://lists.wpkg.org/mailman/listinfo/wpkg-users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20130712/e9573646/attachment-0003.html>