Rsync should not be responsible for detecting what a filesystem can handle.
That makes the most sense to me. There are countless filesystems, each
with their own quirks, and countless mkfs and mount options which just
multiplies the possible fs behaviors even more. Best to provide controls
Any possibility of a version of rsync that doesn't need RSH or SSH?
rsync already doesn't need rsh or ssh.
* On host A (server, with room to accept big uploads):
Edit /etc/rsyncd.conf, add this to the end:
[hostb]
path = /srv/rsync/hostb
auth users = hostb
Edit
On 6/26/2014 5:36 PM, samba-b...@samba.org wrote:
https://bugzilla.samba.org/show_bug.cgi?id=10675
Summary: rsyncing 2GB file onto fat32 partition should fail
earlier
Product: rsync
Version: 3.1.0
Platform: x86
On 1/13/2014 5:34 PM, Perry Smith wrote:
Ok. I can get the Mac up to version 3 but I'm wondering if
I need to rethink my whole strategy. Since the source is on NFS,
doing a stat on all the files each run may cost me too much
time.
I might need to split it into smaller pieces and then rotate
On 1/13/2014 6:19 PM, Perry Smith wrote:
Yea. Shouldn't be hard to split up. The hard part is some type
of dependable rotation.
You mention pause... I have to disconnect so I assume that would
abort the transfer. But that triggered another question: would
daemon mode help in this situation?
On 5/16/2013 2:38 AM, Paul Slootman wrote:
On Wed 15 May 2013, Brian K. White wrote:
I did in the case when it was only one pattern, but that was just a
simplified example.
The actual job involves too many include and exclude patterns to use
--include --exclude, or even --include-from
Consider the following directory structure
/foo/aaa/*/*
/foo/bbb/*/*
/foo/ccc/*/*
I want to sync all of /foo,
but exclude /foo/aaa
but not exclude any other occurances of aaa or foo/aaa (be they
files or dirs) that might occur within the other dirs /foo/bbb/*
/foo/ccc/* etc
I don't want to
On 5/15/2013 5:17 AM, Paul Slootman wrote:
On Wed 15 May 2013, Brian K. White wrote:
Consider the following directory structure
/foo/aaa/*/*
/foo/bbb/*/*
/foo/ccc/*/*
I want to sync all of /foo,
but exclude /foo/aaa
rsync -avz /foo ${DEST}::root
Firstly, I always recommend
On 5/15/2013 8:35 AM, Paul Slootman wrote:
On Wed 15 May 2013, Brian K. White wrote:
rsync -avz /foo/ ${DEST}::root/foo/
This syntax does work in his case, and is easier to read, because it
ends up using the exact same specification /foo/ and /foo/ for
both source and dest, but the syntax I
To clarify a little more, trying to do deltas locally doesn't actually
get you anything, because you still have to do all the same disk work on
each end locally even if only deltas were sent over the network. If both
ends are the same machine, generating and reintegrating deltas is just
more
On 2/14/2013 5:21 PM, Dag Wieers wrote:
On Thu, 14 Feb 2013, Brian K. White wrote:
On 2/14/2013 9:50 AM, Dag Wieers wrote:
Since a --direct-io feature was requested a few times the past decade
with little response and the actual patch is quite trivial, I patched
both v3.0.9 and master
On 2/14/2013 9:50 AM, Dag Wieers wrote:
Hi,
Since a --direct-io feature was requested a few times the past decade
with little response and the actual patch is quite trivial, I patched
both v3.0.9 and master branch and included the patches here.
If this functionality is acceptable I don't mind
were using screen, then you don't need to
put nohup before the command and you don't need to put after the
command.
Btw, Brian K. White, that looks familiar. You a member of the opensuse or
postfix lists?
Yep opensuse
--
bkw
--
Please use reply-all for most replies to avoid omitting
On 4/12/2012 3:36 PM, Joachim Otahal (privat) wrote:
it has not been mentioned: nohup !
Yes it was.
--
bkw
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read:
You can try to switch to faster filesystems (reiserfs/ext4/btrfs/zfs)
and enable metadata performance options and do other tuning steps
(dir_index, noatime) and upgrade disks and ram etc, but mostly, with a
frankly unrealistic business requirement like that, you have to either
tell business
On 4/11/2012 10:05 PM, Chris Arnold wrote:
I hopethis hope this makes sense. How do you make rsync run even when not
physically connected to the server? In other words, I run rsync from the
terminal via vnc and when I log out of the connection, rsync stops running. Is
there a script or
On 3/7/2012 3:05 PM, Thomas Guyot-Sionnest wrote:
On 17/02/12 01:58 PM, grarpamp wrote:
Side question: Does anyone know the probability of generating a file with
the same md5 and sha256 which is still looks valid with the expected content
Uhh, zero. Problem is, the author never bothered with
Same problem ftp servers have had since decades ago.
And the answer was (initially) to provide a ls-lR file in the top level
directory or in every directory and educate users to use it. Perhaps you
could enforce that by removing the ability to browse/list, but not the
ability to download
On 11/25/2011 11:23 PM, samba-b...@samba.org wrote:
https://bugzilla.samba.org/show_bug.cgi?id=8416
--- Comment #3 from Cristian Rodríguezcrrodrig...@opensuse.org 2011-11-26
04:23:34 UTC ---
There is a quirk to be aware of in this systemd unit.
Rsync areturns with non-zero (code 20) exit
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
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 the root of the transfer, --include=/tmp
On 11/21/2011 3:09 PM, Brian K. White wrote:
pushfile /path/to/thing
pushfile /path/to/thing host
pushfile /path/to/thing
OR
pushfile /path/to/thing host
--
bkw
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https
On 11/15/2011 4:15 AM, Voelker, Bernhard wrote:
Brian K. White wrote:
On 11/14/2011 2:29 AM, Voelker, Bernhard wrote:
rsync -avx --delete --include=/file --exclude='*' . host2:deltest/.
This didn't work for me, although one difference is my script specifies
a path instead of . Does
On 11/14/2011 2:29 AM, Voelker, Bernhard wrote:
rsync -avx --delete --include=/file --exclude='*' . host2:deltest/.
This didn't work for me, although one difference is my script specifies
a path instead of . Does this only work with literally . in the
places above?
My script parses the
Is there any way to specify a file to be deleted on the remote side
explicitly by name?
I would have thought that deleting the file locally, the rsyncing the
non-existing file with --del would have resulted in the remote file,
which does exist being deleted.
I have a general purpose script
On 11/11/2011 5:15 PM, Carlos Carvalho wrote:
Brian K. White (br...@aljex.com) wrote on 11 November 2011 15:59:
Is there any way to specify a file to be deleted on the remote side
explicitly by name?
I would have thought that deleting the file locally, the rsyncing the
non-existing
On 10/26/2011 12:39 AM, Alex Jurkiewicz wrote:
Any comments?
On Thu, Oct 20, 2011 at 3:59 PM, Alex Jurkiewicza...@jurkiewi.cz wrote:
Hi all,
These two patches change how rsync handles temporary files on the receiver
side. The first patch adds a static token to rsync's temporary filenames.
The
On 10/19/2011 6:58 PM, Cameron Simpson wrote:
On 19Oct2011 12:02, Benjamin R. Haskellrs...@benizi.com wrote:
| On Wed, 19 Oct 2011, Kevin Korb wrote:
|Because it is an even bigger joy to be able to type 'ssh newhost'
|and have it just work even though you can't talk to newhost. You
|can do
On 10/19/2011 11:38 PM, Cameron Simpson wrote:
On 19Oct2011 22:14, Brian K. Whitebr...@aljex.com wrote:
| On 10/19/2011 6:58 PM, Cameron Simpson wrote:
|On 19Oct2011 12:02, Benjamin R. Haskellrs...@benizi.com wrote:
|| rsync has to parse the URL you're passing. The fact that it then
|| takes
On 9/15/2011 1:17 PM, Alexander Dahl wrote:
Hei hei,
Am 08.09.2011 07:09, schrieb Michael_google gmail_Gersten:
When I signed up for the rsync mailing list, I was not expecting to
get all the samba bugs as well.
Me too.
Is it possible to be on just the rsync mailing list, without being on
On 8/1/2011 4:30 AM, Bjorn Madsen wrote:
I thought other might benefit from this lesson learned and thought it
maybe should be added to the man-pages.
I thought my network connection was glitchy and hence set rsync up for
--timeout=120 but I found out that I was actually causing the glitch
with
On 7/15/2011 2:42 PM, Matthias Schniedermeyer wrote:
On 15.07.2011 13:10, Donald Pearson wrote:
Matthias,
A vpn tunnel is an interesting idea. Do you know how long you're able to
keep rsync in limbo before it will give up?
I haven't really tried. But it was about 15 Minutes the one time it
On 7/12/2011 11:10 AM, Donald Pearson wrote:
@Eberhard: I understand what you're trying to say, but in this
environment the reality is rsync reaches and impasse where it is unable
to get beyond work that has already been completed before link failure
cuts it off again.
@Leen: A combination of
On 6/18/2011 8:31 AM, Andre Majorel wrote:
Is there a way to make rsync unconditionally transfer files,
i.e. create them anew even if the target already exists and is
identical to the source ?
rsync -I looks closer but still avoids transferring the files.
-IW
What I don't understand is why
On 6/6/2011 12:54 PM, Paul Slootman wrote:
On Mon 06 Jun 2011, Cliff Simon wrote:
Hm...I´m using 3.0.3 at the Dest-Server, but now I saw that the Source-Server
has 2.6.9
Do I have to enable incremental recursion and from which version is incremental
supported?
Both ends have to be at
On 6/2/2011 11:28 AM, Matt McCutchen wrote:
On Wed, 2011-06-01 at 17:08 -0400, Brian K. White wrote:
There are other problems too, relating to the difference between This
directory was deleted from the source and so you DO want to delete it in
your mirror., vs This directory was removed only
I like the built-in idea as I don't happen to use rsync via inetd/xinetd
or any other on-demand starter.
It's not an actual problem for me, today, but that's no excuse to avoid
doing the right thing once you recognize it.
--
bkw
On 5/31/2011 1:15 AM, samba-b...@samba.org wrote:
On 6/1/2011 3:26 PM, Matt McCutchen wrote:
On Wed, 2011-06-01 at 14:57 -0400, Brian K. White wrote:
I like the built-in idea as I don't happen to use rsync via inetd/xinetd
or any other on-demand starter.
It's not an actual problem for me, today, but that's no excuse to avoid
doing the right
On 4/25/2011 8:10 AM, Alistair Dsouza wrote:
The two rsync calls had a delay of 180 seconds between them but when the
issue was seen the debug prints from the second rsync call were
interspersed with the debug logs of the first rsync call. Our system
startup scripts start just one instance of
On 11/14/2010 12:20 AM, Ben Gamari wrote:
On Sun, 14 Nov 2010 14:09:29 +0900 (JST), KOSAKI
Motohirokosaki.motoh...@jp.fujitsu.com wrote:
Because we have an alternative solution already. please try memcgroup :)
Alright, fair enough. It still seems like there are many cases where
fadvise
On 8/18/2010 9:18 PM, Vanitha wrote:
The exact syntax is as below
Rsync -r -a -e “ssh -l u...@host1” -h /home/xx/dir-name
u...@host2:/home/xx/dir-name
I doubt it.
--
bkw
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options:
On 8/14/2010 3:09 AM, Matt McCutchen wrote:
On Fri, 2010-08-13 at 11:26 -0400, Brian K. White wrote:
I have sample data that exposes this repeatably:
http://lists.samba.org/archive/rsync/2008-October/021889.html
Thanks, but we figured out the problem several months ago and it should
be fixed
I have sample data that exposes this repeatably:
http://lists.samba.org/archive/rsync/2008-October/021889.html
If you place old/file.dat on a remote box and then try to overwrite it
with new/file.dat using rsync -az and any other options except --no-z or
-W, it will fail almost immediately,
What is the general recommendation for compression when using ssh?
Is it a wasteful performance hit to have both ssh and rsync do compression
(when using rsync over ssh)?
If so, is there a clear prefference which is more efficient, rsync or ssh?
Brian K. White -- [EMAIL PROTECTED] -- http
the 2gig file to update, nothing else.
Of course I manually fixed the problem by deleteing the 2gig file from the
backup machines and so tonights rsync should re-create the 0-byte versions
and update the other files no problem, but I just wanted to log the bug.
Thanks
Brian K. White -- [EMAIL
On Wed, Jun 11, 2003 at 04:16:38PM -0400, Brian K. White wrote:
...
2.5.6 (protocol 26) from cvs on SCO Open Server 5.0.6
both machines are the same version of OS and the same copy of rsync.
...
file on LIVE is 0 bytes
file on BACKUP is 2 gigs
on BACKUP you run:
rsync -az
might find that it temporarily
swells beyond 2gb and then goes back to the right size. If yuor OS
barfs at that time ... then you get a problem.
Tomasz
On Sun, Jun 15, 2003 at 09:51:13PM -0400, Brian K. White wrote:
On Wed, Jun 11, 2003 at 04:16:38PM -0400, Brian K. White wrote:
...
2.5.6
I had to do was delete the 2gig file but I just wanted to
report the finding.
thanks
--
Brian K. White -- [EMAIL PROTECTED] -- http://www.aljex.com/bkw/
+[+++[-]-]+..+.+++.-.[+---]++.
filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
--
To unsubscribe
48 matches
Mail list logo
