Hi all, I've restructured a bit the /etc/systemimager/bittorrent.conf adding some options and I've included the si_installbtimage command inside the /etc/init.d/systemimager-server-bittorrent script as suggested by Bernard.
In this way the user can start/stop/status the tracker and the seeder on the image server in one shot (in particular stop the seeder, that it wasn't possible in the previous implementation...) The images and the overrides to be distributed via BitTorrent must be listed in BT_IMAGES and BT_OVERRIDES parameters in bittorrent.conf. To resolve the update issue (to keep synchronized the BT tarball with the files on /var/lib/systemimager/images) I've simply added the option BT_UPDATE=y|n to bittorrent.conf. If BT_UPDATE=y the tarballs are re-created _all_ the times the bittorrent daemon starts. So the user can perform a resynchronization setting that value and running: /etc/init.d/systemimager-server-bittorrent restart Let me know if you have other ideas to be implemented, if you like the default settings in bittorrent.conf and if some option needs additional documentations, descriptions, etc... ASAP I'll update also the howto on wiki, even if the update should be very easy... now there are less steps to do than before... ;-) Cheers, -Andrea Bernard Li wrote: > Yup, that works. > > I _think_ after this is implemented we can release 3.7.3 - unless you > have any other things waiting to be checked in? Might be good to fix > that si_monitortk previous message issue on x86_64 and possibly ia64 > tough. > > Cheers, > > Bernard > >> -----Original Message----- >> From: Andrea Righi [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, May 09, 2006 9:19 >> To: Bernard Li >> Cc: Brian Elliott Finley; [email protected] >> Subject: Re: [Sisuite-devel] ia64 success! >> >> Bernard Li wrote: >>> Hi Andrea: >>> >>> Perhaps doing update all the time is the best way - perhaps we can >>> add this as a configuration option. >>> >> Yes, the option seems good. Maybe we could put it in >> /etc/systemimager/bittorrent.conf... >> >>> How about we break this into 2 components - one is the seeder which >>> only cares about starting/stopping the seeder, and the other is a >>> command line tool which updates the tarball (with the --force option >>> to always update). >>> >>> In that case, if the user decides that he has a recent enough >>> computer and doesn't mind updating the tarball all the time, it can >>> be set in the configuration, otherwise, the user has to manually >>> update it if he/she has made modifications to the image before >>> starting the seeder. >>> >> Yes, I think it's the better solution, in this way, if I've understood >> well, we can implement the daemon on top of the current >> infrastructure. >> The daemon has only to run si_installbtimage with the >> opportune options >> when starting and kill si_installbtimage process when stoppping (maybe >> displaying bandwidth/upload informations with status...). >> >> Cheers, >> -Andrea >> > ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sisuite-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
