lease undo your change. Defining _LARGE_FILES as is done in
rsync.h means everyone will be impacted (Solaris, HP-UX, IRIX, Linux,
FreeBSD, Tru64 UNIX, ...). Discussion has already occurred on this
list about LFS support:
http://lists.samba.org/pipermail/rsync/2000-May/002182.html
http://lists
On Sat, Mar 17, 2001 at 11:22:31AM +1100, Martin Pool wrote:
On 16 Mar 2001, [EMAIL PROTECTED] wrote:
ICK! Please undo your change. Defining _LARGE_FILES as is done in
rsync.h means everyone will be impacted (Solaris, HP-UX, IRIX, Linux,
FreeBSD, Tru64 UNIX, ...). Discussion has already
On Fri, Jun 01, 2001 at 08:44:18AM -0500, Dave Dykstra wrote:
On Thu, May 31, 2001 at 03:29:42PM -0700, Adam McKenna wrote:
The Problem:
Since the script runs once a minute, it is possible for the rsync to start
while a file is still being transferred to us. What appears to happen
Patch to set RSYNC_NAME in rsync.h. It adds a new option to configure,
--with-rsync-name, that takes a string that is used to replace
RSYNC_NAME. The default is rsync.
--
albert chin ([EMAIL PROTECTED])
-- snip snip
Index: configure.in
On Wed, Jul 18, 2001 at 03:42:11PM -0700, Sudarshan Ramaswamy wrote:
Hi
I am new to rsync. I have installed rsyn2.4.6 in my home directory. I
can rsh to any machine without any passwd as we have NIS .
rsync works perfectly on my local machine ie if
I rsync within the same machine
While potentially a useful option, you wouldn't want the protocol to
automatically always check for it, since it would preclude rsync on
This extension need not break any existing mechanism; if the hash of
the receiver's copy of the file doesn't match the start of the
sender's file, the protocol
I just confirmed that data corruption can occasionally occur with
rsync 2.5.0 when the -z option is used. My command was the following:
rsync -vaz --partial --block-size=65536 --checksum remote:/path/ /localdir
The files consisted of a year's worth of email (262MB), broken into
one file
Please keep the two directories that caused the problems, if they have
not already been overwritten.
They've been overwritten, but the problem is easy to recreate.
I did diff the correct and incorrect versions of the file. A whole
bunch of instances of the word for were turned into foF. Weird.
I just ran into the same corruption problem with 2.5.1pre3. Again, it
only happens when I use large checksum block sizes (65536) *and*
request compression (-z).
Because the corrupted file has a correct size and timestamp, I have to
re-run rsync with the --checksum option (and with either
My apologies, this fix went in after 2.5.1pre3. Would you please try
either using CVS HEAD, or
./configure --disable-debug
Just tried that. (Yes, I rebuilt both ends). Still broken. Here's the
diff between a corrupted and correct version of my rsync mailing list
mbox:
bash-2.03$ diff
This really is a minor point because as Martin pointed out, the fact that
rsync's pipelining would be defeated means that the idea would have a
drastic effect on throughput.
Okay, everyone has convinced me that my problem (excessive traffic in
the reverse direction) is best solved by simply
On Tue, Dec 18, 2001 at 03:53:07PM +, Terry Raggett wrote:
Anyone have problems with getaddrinfo under AIX4.3? I have built 2.5.0 under
linux, HP and VPP without too much in the way of problems. However, AIX4.3
version builds OK but doesn't execute getaddrinfo correctly.
What error do you
On Wed, Dec 19, 2001 at 10:20:52AM +, Terry Raggett wrote:
On Dec 18, 22:37, [EMAIL PROTECTED] wrote:
Subject: Re: rsync-2.5.0 getaddrinfo in AIX4.3?
On Tue, Dec 18, 2001 at 03:53:07PM +, Terry Raggett wrote:
Anyone have problems with getaddrinfo under AIX4.3? I have built 2.5.0
:
bash-2.05a$ rsync -vaz homer-rr.ka9q.net:wwv_wwvh .
receiving file list ... done
wwv_wwvh
rsync: connection unexpectedly closed (69 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(151)
bash-2.05a$
This was with 2.5.3 on both ends. Here's the build log:
Script
pulling 2.5.3 from the distribution
site until it can be updated.
Thanks!
Phil
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Title: Free Trial for TVStripper
Watch North America's Sexiest Strippers take it all off for Free.
I have ran rsync once and replicated 25 gigs of data. Now when I run rsync
again it goes through all the files again. I thought it was only suppose to
get new or changes files. Is there a special switch that I am suppose to
use?
Thanks
SKP
--
To unsubscribe or change options: http
Sorry I did not put in the command earlier. Here is the command I used for
the first and second run
Rsync --verbose --stats --recursive 192.168.1.1::home /usr/home/fileserver/
Though the second time long less time than the first time (ran for3 days) it
still took over 4 hours.
I need to run
.
That, if my understanding is correct, should leave us with 3.5G of available
memory to draw upon.
Running rsync with --progress, (v2.5.6 I believe - just downloaded it a few
days ago) shows us that we reach a little over 8 million files before the
server starts telling us its killing processes because
I am using rsync to backup Maildir directories. Since it is very active,
some files are deleted (and some are added as new mail arrive) from the
time that the list of files are collected and the time of the actual
operation.
I have check the mailing list archive and I did not see a clear answer
The message contains Unicode characters and has been sent as a binary attachment.
data.pif
Description: Binary data
Hi all,
wouldn't it be much more comfortable if rsync would delete every sent file
just after completing the single file transfer?
Thus one could transfer files that could be processed by the receiver and
there get moved or deleted avter processing.
With large directories and e.g. wireless
Hello again,
I'm just starting a huge rsync-projevt and it seems to get even more
complex and syncing lots of MBs each day...
My customer scans images, and puts them into dir a.
Someone else checks the pictures and puts them into dir b.
Next steps are removing optical errors, keywording
Hi!
I am running rsync 2.6.4 (on Debian sarge) and I am experiencing a
strange behaviour.
I am trying to create an identical filetree on the same filesystems with
the single files being hardlinks to the source like this:
rsync -vaH --progress --delete --stats --numeric-ids -x
--link-dest=/path
changing into the destination directory.
Now I see that line in the man page. Sorry for the confusion.
Greetings
--
Robert Sander
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Hi!
It's me again with another --link-dest issue:
I am using dirvish (www.dirvish.org) to create daily backup on disk
images.
dirvish is using rsync with --link-dest pointing to the last good image.
This creates images with hardlinks to unmodified files. So far so good.
Now I want to create
.
And it does not like symlinks, bind mounting or any other tricks we
tried so far...
Greetings
--
Robert Sander
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
On Mon, Apr 30, 2007 at 07:17:52PM +0400, Mark wrote:
Hi,
I use rsync with such options:
OPTIONS=-a -u -z -v -S --delete-during --ignore-errors \
-b --backup-dir=${PATH_BACKUP}/${DATE_YESTERDAY} \
--exclude-from=$IGNORE
[skip]
Do you know what to do it to make empty
Hi!
I'm trying to create a filter file for rsync what saying which dirs to
copy. For example i need only /lib and /var/lib dirs from remote server.
I say:
rsync -f . /tmp/rsync_dirs --dry-run --verbose remote:/
/local_dir/.
File /tmp/rsync_dirs looks like:
+ /lib/
+ /var/
-! /var/lib
Thank you, it works.
But if I want to delete only certain files or dirs from remote side?
example:
$ tree dirA/
dirA/
|-- dir2
| `-- file3
|-- file1
`-- file2
$ tree dirB/
dirB/
|-- dir2
| `-- file3
|-- file1
|-- file2
`-- protect1
$ rsync -av --dry-run --delete-excluded -f . filter dirA
Well, I must say that this must by bone by rsync.
That's because I'm creating small automation system,
part of it is rsync-based.
Yes, I can write rm -r dirB/dir2, but this will break consitency
of the whole system and removes some features that I need.
I do need to delete dirs and files by rsync
it the daemon) but
this does not terminate all the rsync server processes.
Experimenting and reading the documentation it seems that rsync in daemon
mode spawns a worker process for each connection and they in turn spawn
further workers. When the daemon is killed the connection leader(s)
re-parent
to modes
which may be symbolic or octal/numeric. Accordingly I tried
incoming chmod = D755,F644
but this resulted in 'Invalid incoming chmod directive: D755,F644'.
Should I report an issue with the rsync man pages suggesting that either
strings is changed to symbolic modes or that rsync is enhanced
-Original Message-
From: 4way...@gmail.com [mailto:4way...@gmail.com] On Behalf
Of Wayne Davison
Sent: 17 December 2010 11:31
To: rs...@catcons.co.uk
Cc: rsync@lists.samba.org
Subject: Re: rsync server: incoming chmod usage
On Wed, Dec 15, 2010 at 6:54 AM, rs...@catcons.co.uk
Date: Wed, 29 Dec 2010 10:27:07 +0100
From: Alexander Dahl p...@lespocky.de
To: rsync@lists.samba.org
Subject: Re: rsync server bootscript - stop and status considerations
Message-ID: 0ltbwl-1qukfi1brz-012...@mrelayeu.kundenserver.de
Content-Type: text/plain; charset=windows-1252
Hello
-Original Message-
From: 4way...@gmail.com [mailto:4way...@gmail.com] On Behalf
Of Wayne Davison
Sent: 17 December 2010 11:31
To: rs...@catcons.co.uk
Cc: rsync@lists.samba.org
Subject: Re: rsync server: incoming chmod usage
On Wed, Dec 15, 2010 at 6:54 AM, rs...@catcons.co.uk
Hallo Hannes
"man 5 crontab" is your friend ;-)
Am 12.07.2019 um 10:56 schrieb Hannes Hutmacher via rsync:
But, when I add the script in cron to start it at 1am at night it
takes 7 - 9 hours and I see up to 180 processes. When I look in top I
see a hight load of 60 - 80 and 40 - 60
Rainy Days via rsync wrote:
> Hi,
>
> My company have been using rsync to sync our file to a backup server (running
> rsync daemon), and now we would like to store them encrypted.
> I found some thread that discussed this issue but they are pretty old (about
> 10 yea
Here is the missing attachment ;-)
On Fri, 2023-09-22 at 21:01 +0200, rsync--- via rsync wrote:
> On Fri, 2023-09-22 at 07:37 -0400, Kevin Korb wrote:
> > So I decided to do a quick test using the Linux kernel source tree since
> > it has lots of files.
>
> Excellent idea
narios...
> I duplicated a tree, used 'find . -type f -exec
> chmod 444 {} +' to make read only files for rsync to want to chmod, then
> used cp -al to make several duplicate trees using hard linked files.
> [...]
> But also, I did not experience the problem you are describing. My su
On Thu, 2023-09-21 at 20:08 -0400, Kevin Korb via rsync wrote:
> I have heard in the past that rsyncing an empty dir over a tree to
> delete the tree is faster than an rm -rf but I can't say I have ever
> benchmarked it to get any actual numbers.
This **may** indeed be a myth (for a
Context
---
I am one of the active developers of the open source application "Back in Time"
which uses "rsync" as backend and I want to fix an open issue:
"Back in Time"-Bug:
https://github.com/bit-team/backintime/issues/994#issuecomment-1724211507
&q
I want to recognize and handle some rsync error messages
in my log files (containing also the --itemize-changes output)
on different computers with different language/locale settings.
Can I rely on rsync to create only English error messages
to have a stable pattern to recognize?
PS
On Thu, 2023-12-14 at 14:09 -0500, Kevin Korb wrote:
> Unfortunately, exit 23 litterally just means something else went wrong
> and might have scrolled off of the screen if you have rsync listing
> files (--verbose or --itemize_changes). Essentially, it is anything
> that doesn't
I am trying to find a solution for the open source Linux software
"Back In Time" (https://github.com/bit-team/backintime)
where we evaluate the rsync exit code when taking a backup via rsync
and inform the user that an error has occured.
Questions:
1. Is there full list of possib
Hello!
Agood day to you all. I got some error messages from rsync:
rsync: error writing 4092 unbuffered bytes - exiting: Connection reset by peerrsync: read error: Connection reset by peerrsync error: error in rsync protocol data stream (code 12) at io.c(162)rsync error: error in rsync protocol
Hello!
A good day to you all. i've installed rsync-2.5.6 on a Red Hat 9.0 box(server) and am
using rsync 2.5.6 on a Red Hat 6.2 box(client). In the middle of the rsync transfer, i
get the error on the client saying that the server unexpectedly close the connection.
Upon checking the logs
rsync 2.5.6 security advisory
-
December 4th 2003
Background
--
The rsync team has received evidence that a vulnerability in rsync was
recently used in combination with a Linux kernel vulnerability to
compromise the security of a public rsync server. While
I've released rsync 2.6.0pre2. This should be the final pre-release
before 2.6.0 goes final (which is scheduled to happen on January 1st).
If you'd like to assist in making the final release smoother, please
try this out and let me know if you encounter any problems:
http://samba.org/ftp/rsync
I've released version 2.6.0 of rsync. Two important things to note
in the new release:
1. The default remote shell is now ssh unless you tell
the configure you want to use something else.
2. Some bug fixes in the include/exclude code, while making
things work properly
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Rsync version 2.6.1 has been released. It is primarily a performance
release that requires less memory to run, makes fewer write calls to
the socket (lowering the system CPU time), does less string copying
(lowering the user CPU time), and also reduces the amount of data
that is transmitted over
the_message.cpl
Description: Binary data
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Rsync version 2.6.2 has been released. It is a bugfix release that
mainly fixes a bug with the --relative option (-R) in 2.6.1 that could
cause files to be transferred incorrectly. This only affected a source
right at the root of the filesystem, such as / or /* (using . as
the source after
` like so (for bash):
yesterday=`date -d yesterday +%Y%m%d`
Then on the server I delete all backup.$eightdaysago directories via a cron
job.
HTH,
Joe
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
.
Thus, that's still the old rsync running. Perhaps it didn't really get
stopped? Or perhaps it is running via inetd?
Given how often rsync versions change and how much functionality goes
into each new one (yay!), I wonder if it might not be such a bad idea
to have the rsync version embedded
Date: Mon, 12 Jun 2006 14:18:00 -0400
From: Matt McCutchen [EMAIL PROTECTED]
On Mon, 2006-06-12 at 10:58 -0700, Chuck Wolber wrote:
On Mon, 12 Jun 2006, Brad Farrell wrote:
Is there a way with rsync to encrypt data at the source before
transmitting? Not talking
that they -do- trust.
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
hello,
i've rsync installed:
rsync version 2.6.9pre3 protocol version 29
Capabilities: 64-bit files, socketpairs, hard links, symlinks,
batchfiles,
inplace, no IPv6, 32-bit system inums, 64-bit internal inums
i'm PULLing via rsync+ssh from BoxA to BoxB, eg
what),
but the receiving side's list will only contain this string if rsync
believes that it is running in super-user mode with ownership being
preserved.
while rtfm'ing and poking around, i believe i've stumbled onto the
problem -- or, at least, a causal component.
the boxes -- in this case
ok, so this is not entirely an rsync question. but, it seems the
'crowd' most familiar w/ hard-linking are the rsync crowd. so ...
i'm doing rsync + incremental backups to a local drive.
the incremental steps, currently, use the
rsync REMOTE_DIR OLD_DIR
... time passes ...
cp -al OLD_DIR
hi,
i've been coming up to speed on rsync+ssh, incremental backups, etc etc.
atm, all working great across *NIX boxes.
but, i've recently been reminded that there are 'issues' with
poor/failed backup of osx-files' metadata, w/ rsync other tools:
http://blog.plasticsfuture.org/2006/04/23/mac
hi,
it seems there's a more-recent solution, referenced here:
http://www.lartmaker.nl/rsync/
that points out:
Since OS X 10.4 (aka Tiger) the MacOS ships with a modified
version of rsync. An added option, -E, enables the transfer of
extended attributes.
exploring, the current apple
i've built up rsync on both opensuse osx from src.
on osx, it's v2.6.3 w/ both apple's Extended Attributes patches:
http://www.opensource.apple.com/darwinsource/10.4.8.ppc/rsync-24/patches/EA.diff
http://www.opensource.apple.com/darwinsource/10.4.8.ppc/rsync-24/patches/PR-3945747
and the 'lartmaker' fix (iteself, slightly fixed ...):
applied.
What exactly did you have to fix ?
after applying,
http://www.opensource.apple.com/darwinsource/10.4.8.ppc/rsync-24/patches/EA.diff
http://www.opensource.apple.com/darwinsource/10.4.8.ppc/rsync-24/patches/PR
, in part, by installing the
dependencies i'd mentioned.
if need be, i can reproduce the build output with missing
symbols/headers errors and post it.
thanks.
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart
First, to be clear, you are building rsync on Mac OS X, right?
You need at least Tiger.
absolutely. i've an up-to-date osx 10.4.8 install, w/ latest XTools
etc from Apple.
Don't enable acl support on osx. It doesn't work. You probably don't
have ACLs on your files anyways as it has
://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Sorry I haven't looked into this, but atm I just don't have the time.
thanks for the update. personally, atm, i'd love to see just HEAD's
mtime (finished?) support rolled into a 'official;' rsync release.
It also seems like any solution will necessarily drop information.
osx keeps track
of the images to go to each location in
that directory.
to accomplish this goal, i placed the following line in my crontab on the
master.
(time for this to execute) rsync -e ssh -avzuLE --copy-links
/Volumes/Storage/lincoln/ 172.16.40.200:/images/
perhaps there's a problem with my syntax? any help
and we're done.
now, to see if it actually makes rsync3 'happy' ...
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
, and works just
fine when/as used by rsync3 -- or elsewhere.
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Date: Fri, 16 Mar 2007 02:30:33 -0700 (PDT)
From: syncro [EMAIL PROTECTED]
Thanks alot! That's what I wanted to hear ;)
We want to have an always-up-to-date-copy thus rsync every minute and not
just at night. However my preventive measure will be a forbiddance of
sharing
was
flushed and allowed to regenerate on its own with a working clock.]
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
on that side as
recorded in the cache. Clock synchronization between the two sides is
irrelevant.
Okay, but that's still unreliable. Backward clock steps -can- happen;
only in Multics is it (mostly) impossible (because a backwards step
would destroy the filesystem). But since rsync probably
, whereupon the clock
ran away. But since it was -almost- holding it together, for days or
weeks at a time...
And the machine was an NFS server. So in fact this scheme would have
been leading to a whole bunch of sporadic why was this cache
inaccurate? failures for a long time if rsync had been using
out. :\
If you (anyone) can work it out and/or bring it into
rsync as a new feature, that would be great. Please
keep the author and myself in the loop!
Do a search for faster-dupemerge; you'll find mentions of it in the
dirvish archives, where I describe how I routinely use
Date: Mon, 05 Nov 2007 13:17:32 -0500
From: Matt McCutchen [EMAIL PROTECTED]
I think rsync should omit the speedup on a dry run. The attached patch
makes it do so.
I worry about those trying to write things that parse rsync's output;
if -n changes the output format
(or some more-reasonable estimate) anyway?
Sure, all kinds of differences haven't been computed, but...
Rsync could estimate an upper bound on how much a real run might send by
adding the size of the data that wasn't transferred (regular file data
and abbreviated xattrs) to the amount
client to affect the
security
breach. I admit I am no whiz at securing the rsync server. Once we had
it
setup to run in daemon mode we assumed the ssh tunnels would provide all
that we need. We over looked this one issue however.
Are users supposed to be running any arbitrary rsync
I've got a problem for which the combination of -R and --link-dest
doesn't seem to be quite enough---and I may have discovered a few
small bugs as well; test cases are below.
[And if someone has a scheme for doing this that doesn't involve rsync
at all, but works okay, I'm all ears as well---I'm
who might need
to move such extensively-hardlinked filesystems.]
Okay, so the above shows that --link-dest without -R appears to work,
BUT---
how come there was no actual output from rsync when it created
dst/a/2/foo?
Correct side-effect (foo created, with correct inode
sorry for the confusing subject line. i couldn't think of a better way to say
it.
i'm wondering if rsync can perform the following action:
Compare contents of Directory A (master) to Directory B and copy any
differences from Directory A to Directory C (example below)
Directory A:
foo
bar
Hello and thanks to all who so generously assist on this great list.
test command:
rsync -avm --del --prune-empty-dirs --compare-dest=/Users/generic/Desktop/B
/Users/generic/Desktop/A/ /Users/generic/Desktop/C
produces a large number of directories and nested directories on the
destination
Robert DuToit wrote:
On Apr 6, 2010, at 9:14 AM, Benjamin R. Haskell wrote:
On Mon, 5 Apr 2010, Robert DuToit wrote:
Hi Matt,
I set up a simple test with a nest of directories ( aa bb cc
dd ee) with 1 file in each. running rsync from OS 10.6 to
another Mac with OS10.5 there seems
thread would otherwise be noticed.]
So, having tried your solution 1 and solution 2 (long pause while Matt
and/or others page in their state, probably by visiting something like
http://www.mail-archive.com/rsync@lists.samba.org/msg23196.html :),
I can't make either one work.
Here's a transcript
If you're thinking about changing the way attrs work, here's a
question for you. I just recently started trying to use them for the
first time, in backing up a Windows host via a wrapper script that
runs the remote rsync under Cygwin on the Windows side, by mounting
the source disk as a VSS
if you have a backup server with rsync running in daemon mode - is there a way
for a client to obtain information about free diskspace via rsync?
Create a cron job on the server that builds a file with the available
disk space, output to a file under one of the read-only modules. Then
your
terabytes of random bits to the far machine and use an nc tunnel
to redirect them back to the sending machine and compare what you get.
That may implicate the network hardware, the remote machine, whatever,
but it would take rsync itself out of the picture. Or, if you don't
want to set up the reflected
consideration.
> The problem is that if you transfer from a filesystem that has nanoseconds
> to one that does not support it, rsync would consider most of the files to
> be constantly different, since the nanosecond values would only match if
> the source file happ
> Date: Sun, 24 Jan 2016 15:43:20 -0800
> From: Wayne Davison <wa...@thedavisons.net>
A couple questions below; please bear with me.
> No, if you do a ext4 -> ext4 copy, rsync has set the matching ns info for
> transferred files since 3.1.0. There was a case
> older filesystem (e.g. ext3) that doesn't support nanoseconds.
Thanks for the patch!
Just FYI, this comment is true but incomplete---the scenario I was
describing was straight ext4-to-ext4 copies and/or backups. The
timestamp problem I currently see with those is because rsync was
throwing away th
It's possible to have situation when current directory is not needed for
rsync operation (using absolute path on lazy mounts / being in deleted
directory).
rsync should not fail in such cases
---
util.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/util.c b/util.c
24, 2023 at 1:14 AM
*To:* .
*Cc:* rsync@lists.samba.org
That's how rsync operates normally; you shouldn't have to do
anything to get that behaviour. That's kind of the whole thing it's
for.
If you're *not* seeing that behaviour, something weird is going on.
Possibly one side or the other
I'm using rsync to copy files from a source folder to a destination
folder. It works fine. But, to save some time, what options should I
use to only update or copy (to the destination) files that are new
and/or have a new time stamp on them?
Here's the code I use below (pretty sure the -n
;-i>:
rsync -avhHXASDin --del /mnt/ /foo/mnt/
I get:
=
sending incremental file list
.fx usr/bin/ping
.d...a. var/log/journal/
sent 263,31K bytes received 1,14K bytes 528,90K bytes/sec
total size is 294,92M speedup is 1.115,21 (DRY RUN)
Hi,
thanks for the information. Shall I file a bug report at
https://github.com/RsyncProject/rsync/issues ?
Yours
lopiuh
Am Mo., 3. Juni 2024 um 15:57 Uhr schrieb Paul Slootman via rsync
:
>
> On Mon 03 Jun 2024, Kevin Korb via rsync wrote:
>
> > It appears that xattr change
I have so far been unable to get rsync to work properly in a test setup.
Does anyone have any ideas?
Both PCs are running RedHat 7.2.
The Server:
IP Address 192.168.0.202
Server Name: RH72TB
hosts.allow ALL: 192.168.0.201
rsyncd.conf:
[testmodule]
path = /tmp
The Client:
IP Address
hello,
1) ssh is the default protocol of rsync since 2.6.0, so if you are using a new version you should not have to worry about it.
2) check that you used the command as following:
rsync -e ssh @:~/
that should do the trick (worked for me)
m2f
1 - 100 of 3389 matches
Mail list logo
