Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Fri, Aug 17, 2007 at 11:06:26PM -0400, Tom Metro wrote: > In terms of performance, you'd be far better off using rsync. And don't > run rsync against a network mounted file system, as that defeats the > benefits of the rsync protocol. Run an rsync daemon (either statically > or dynamically started) on the workstations. Slightly less efficient but much more secure: run rsync over ssh. rsync -a -e ssh /source/path/ user at remotehost:/destination/path Or use a helper script like this: ---- if [ -n "${SSH_PORT}" ]; then args="$args -p $SSH_PORT" fi if [ -n "${SSH_USER}" ]; then args="$args -l $SSH_USER" fi if [ -n "${SSH_IDENTITY}" ]; then args="$args -i $SSH_IDENTITY fi if [ -n "${SSH_ARGS}" ]; then args="$args $SSH_ARGS" fi exec ssh $args "$@" ---- and set some variables, then call rsync -a -e scriptname /source/path/ remotehost:/destination/path > If you have the disk space, you can then pair this strategy with one of > the snapshot schemes that use rsync, resulting in some degree of > historical archives. rsnapshot is a good keyword. -dsr- -- Every time you give up a right, the terrorists win. http://tao.merseine.nu/~dsr/eula.html is hereby incorporated by reference. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |