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
