Edward Ned Harvey wrote: >> If feasible, you may want to generate MD5 sums on the streamed output >> and then use these for verification. >> > > That's actually not a bad idea. It should be kinda obvious, but I hadn't > thought of it because it's sort-of duplicating existing functionality. > > I do have a "multipipe" script that behaves similar to "tee" but "tee" can > only output to stdout and a file. In my POSIX universe I can just do
zfs send ... | pv | tee >(md5sum) >(sha256sum) | gzip | tee >(md5sum > .md5.zipped) | ssh remote etc. etc. > "multipipe" launches any number of > processes, and pipes stdin to all of the child processes. I normally use > this when creating a large datastream ... I generate the datastream, and I > want to md5 the uncompressed datastream, and I also want to gzip the > uncompressed datastream. I don't want to generate the filestream twice. > Then I will gunzip | md5 to check the sum. > > I also have a "threadzip" script, because gzip is invariably the bottleneck > in the data stream. Utilize those extra cores!!! ;-) > > I plan to release these things open source soon, so if anyone has interest, > please let me know. > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss