Hello all,
Is it possible to compile rsync to be self contained. Meaning, I want
to have 1 binary which will have all its libraries compiled into it
and ofcourse rsync in it. I want to have a self contained version of
rsync.
TIA
--
Please use reply-all for most replies to avoid omitting the
Its an option when you install the port.
Regards
Steve
- Original Message -
From: alexus ale...@gmail.com
To: rsync@lists.samba.org
Sent: Friday, March 13, 2009 2:12 AM
Subject: rsync flags freebsd
is there a way to save special flags in freebsd when using rsync?
for example
I'm using Rsync 3.0.5 between two Debian boxes. I have an rsync
script setup that uses --log-file=mylogfile.log and also I have
specified --log-file-format=whatever. But I can't seem to get the
--log-file-format to be recognized. I don't get any sort of errors,
but the log format that I get is
https://bugzilla.samba.org/show_bug.cgi?id=6183
--- Comment #2 from way...@samba.org 2009-03-13 12:11 CST ---
File too large is an OS error, so you need to figure out why your OS is
returning that. I'd imagine that rsync was not compiled with large-file
support. If so, let me know
https://bugzilla.samba.org/show_bug.cgi?id=6120
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Fri 13 Mar 2009, Jake Wilson wrote:
I'm using Rsync 3.0.5 between two Debian boxes. I have an rsync
script setup that uses --log-file=mylogfile.log and also I have
specified --log-file-format=whatever. But I can't seem to get the
--log-file-format to be recognized. I don't get any sort
Is there a way to be subscribed to this list and NOT get the posts
from samba-b...@samba.org?
According to https://lists.samba.org/mailman/options/rsync/lbutler+rs...@covisp.net
I am only subscribed to this list.
--
The Steve is seen, rightly or wrongly, as the visionary, the
On Thu, Mar 12, 2009 at 10:35:45PM -0400, Matt McCutchen wrote:
The rsync 3.0.5 version of this patch is at:
http://rsync.samba.org/ftp/rsync/patches/fileflags.diff
I've just revised how patches are stored so that I can have patches for
3.0.x as well as 3.1.0dev. Thus, the link you cited is
On Fri, 2009-03-13 at 14:39 -0700, Wayne Davison wrote:
On Thu, Mar 12, 2009 at 10:35:45PM -0400, Matt McCutchen wrote:
The rsync 3.0.5 version of this patch is at:
http://rsync.samba.org/ftp/rsync/patches/fileflags.diff
I've just revised how patches are stored so that I can have
On Fri, Mar 13, 2009 at 06:57:15PM -0400, Matt McCutchen wrote:
I would have thought it more natural to have branches patches-master
and patches-3.0.x in the main repository. Is there any reason you
made a separate repository?
Yes, this way the branch names match and I can tag releases.
Firstly, if this the wrong place to ask this question or if this
question is inappropriate then please accept my sincere apologies.
I am seeking advice regarding the backup of an Windows XP machine.
I have used rsync for years and believe it to be an absolutely amazing
tool on *NIX systems.
Hi list
I was wondering if this is (or could be) possible with rsync. I was
wondering if there was a way to change the bandwidth limit
(--bwlimit=KBPS) dynamically while rsync is running? Could this be
possible maybe with signals like USR1 add 5KBPS and USR2 subtracts
5KBPS? I'm not a programmer,
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project rsync.
The branch, master has been updated
via f8605c5b89720a09b8aa0d5e7aa3ea27b1ebbf4f (commit)
from
Date: Fri Mar 13 21:27:46 2009
Author: wayned
Update of /data/cvs/rsyncweb
In directory dp.samba.org:/tmp/cvs-serv25974
Modified Files:
download.html
Log Message:
Updated to match the latest patches setup.
Revisions:
download.html 1.28 = 1.29
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project Rsync's patches repository..
The annotated tag, v3.0.1pre2 has been created
at b5c1878d570f98294f3d877caeda5f52da0c87de (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project Rsync's patches repository..
The annotated tag, v3.0.1pre1 has been created
at 63ceef78e6994a18cb164e26eadee094184c3fd4 (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project Rsync's patches repository..
The annotated tag, v3.0.2 has been created
at 85e5bba7c069af202f0c6aae7fa8f8c258935748 (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project Rsync's patches repository..
The annotated tag, v3.0.1pre3 has been created
at 4887510e841d7acf2781e57fd791fda9142a157b (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project Rsync's patches repository..
The annotated tag, v3.0.3pre1 has been created
at 75b341a2eddc564d5d0a86e0e58b902ab7d14956 (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project Rsync's patches repository..
The annotated tag, v3.0.3pre2 has been created
at 241763b9fcda70f1f7d019ebf5c35ba2093d0350 (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project Rsync's patches repository..
The annotated tag, v3.0.3pre3 has been created
at 7b876d5122d0cf95d75402c63bd3c42864a5f323 (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project Rsync's patches repository..
The annotated tag, v3.0.5 has been created
at 0fcc01c2d4a3076000b9bbde6ade893207c47ccc (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project Rsync's patches repository..
The annotated tag, v3.0.4 has been created
at 2ae6c60f7c93000ab083c68d6a9324c8501922b0 (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project Rsync's patches repository..
The annotated tag, v3.0.5pre1 has been created
at ed9fc08ebf9458bb675587e42121937a00452442 (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project Rsync's patches repository..
The annotated tag, v3.0.5pre2 has been created
at 7da6c11ce3179d2f5f8818fb38390d1e41f643cf (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project Rsync's patches repository..
The annotated tag, v3.0.1 has been created
at 2c060f068a4cd384ae1ef6709970b542d0b37118 (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project Rsync's patches repository..
The annotated tag, v3.0.3 has been created
at 290cef3859806dc3576c9f4973a19a90bb1627a4 (tag)
27 matches
Mail list logo
