Hi, after tweaking a bit OSCAR multicast deployment started to work. Sort of... When receiving the image, this is done in one huge piece. So the piece is transfered to the client being installed and stored in /tmp/multicast.tar.
After a short while the filesystem (which is a tmpfs) fills up and the whole thing breaks. Looking at the autoinstallscript, it seems that there is no loop over sent chunks, so sooner or later the tmpfs must get filled up by the multicast data. My node is not particularly small, so I'm wondering whether anybody really managed to use the multicast deployment for real life cases where the image is significanlty bigger than the available ramdisk storage. Wouldn't it make more sense to directly pipe the udp-receive output to a tar? Regards, Erich ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Sisuite-devel mailing list Sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
