On Mon 21 Nov 2011, Brian K. White wrote:
On 11/19/2011 9:04 AM, francis.montag...@inria.fr wrote:
On Tue, 15 Nov 2011 23:49:18 +0100 Brian K. White wrote:
nj2:/opt/x # rsync -avvvn --force --delete --include=/tmp
--include=floof/ --exclude='*' /tmp/. co4::root/tmp/.
Detail: /tmp being
On 11/22/2011 6:51 AM, Paul Slootman wrote:
On Mon 21 Nov 2011, Brian K. White wrote:
On 11/19/2011 9:04 AM, francis.montag...@inria.fr wrote:
On Tue, 15 Nov 2011 23:49:18 +0100 Brian K. White wrote:
nj2:/opt/x # rsync -avvvn --force --delete --include=/tmp
--include=floof/ --exclude='*'
Thank you both for your replies,
nothing unexpected in the comments, but I'm certainly glad there were no
bombshells telling me a painful path lay ahead.
We're having an internal discussion about replacing rsync in place vs using
/usr/local/bin. We have a very small team with a lot of
Hello all,
This is my first post to this mailing list. I have been using rsync for a bit
and have it mostly working the way I want.
I have a backup server that I run all scripts from. It rsyncs data from four
different Linux servers via cron. A sample of a script is here:
rsync -avz
Bryan:
I successfully compile rsync under OS X, placing the binary in
/usr/local/bin and the man pages in /usr/local/man.
I rewrote my $PATH and $MANPATH to look in those places first (in
~/.bashrc). That way, when I type rsync at the prompt, it finds the
one in /usr/local/bin and stops looking
Apologies if I missed something in earlier posts, but I wonder if those of you
who are looking to install rsync on your OS X boxes are aware of macports.
http://www.macports.org/
Currently rsync 3.0.7 is available through macports, which would save you the
trouble of compiling, and it would
