<br><br><div class="gmail_quote">On Sun, Feb 1, 2009 at 6:56 PM, David L. Anselmi <span dir="ltr"><<a href="mailto:anselmi@anselmi.us">anselmi@anselmi.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Jed S. Baer wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
And looking around in the clue-talk directory on the server, I see<br>
nothing amiss. But in a tree that size, it'd be easy not to notice it<br>
using visual inspection.<br>
</blockquote>
<br></div>
You could do:<br>
<br>
find . -type f | sort | xargs cksum<br>
<br>
on both the server dir and your dir and see how they compare. That would tell you whether the sync worked (modulo any more recent changes) and also exercise the server file system.<br>
</blockquote><div><br>I wrote a findd (find duplicate) script for this sort of thing. It's old and probably makes excessive use of files, but it works.<br><br> <br></div></div>#!/bin/bash<br><br>sumexec=/usr/bin/md5sum<br>
tempfile=/tmp/$(date | $sumexec | cut -d " " -f1)<br><br>echo "tempfiles: $tempfile"<br><br># Generate md5 sums<br>find . | while read file<br>do<br> if [ -f "$file" ]<br> then<br> echo "checking $file"<br>
$sumexec "$file" >> $tempfile.sums<br> fi<br>done<br><br># Sort files<br>sort $tempfile.sums > $tempfile.sorted<br><br># Get unique entries<br>awk '{print $1}' $tempfile.sorted > $tempfile.sums<br>
uniq $tempfile.sums > $tempfile.uniq<br><br>echo "The following files have matching checksums"<br>echo "This means they MIGHT be duplicates."<br>echo "--------------------"<br>diff $tempfile.sums $tempfile.uniq | fgrep "<" | cut -d " " -f2 > $tempfile.results<br>
uniq $tempfile.results | while read file<br>do<br> fgrep $file $tempfile.sorted<br> echo ""<br>done<br>echo "--------------------"<br><br>rm $tempfile.*<br><br>exit 0<br><br>