rsync is a very useful tool for me to backup from Max OS X
to a linux server. However, would developers please add one
feature:
When rsync runs on an OS X machine and the source files are
in hfs+ (or hfs) filesystem, copy the resources fork to a
file with filename starts with a dot and append
I just tested sending a SIGUSR1 and no joy. Do you send it to one of the
child processes instead of the parent?
-Chuck
On Tue, 27 Apr 2004, John Taylor wrote:
>
> What about returning progress status when rsync receives a SIGUSR2?
> It looks like there is code to return some sort of status
I am using rsync version 2.3.2 on Sun (SunOS 5.8).
And I encountered the following problem that I hope the
guru of rsync on this list can shed light on.
The configuration is depicted as follows:
rsync
Sun data file -> NFS file server (nfs)
|
What about returning progress status when rsync receives a SIGUSR2?
It looks like there is code to return some sort of status when SIGUSR1
is sent. Is this accurate?
-John
On Tue, Apr 27, 2004 at 02:54:43PM -0700, Chuck Wolber wrote:
>
> Just built 2.6.1 and started testing it. Nice job guys.
I knew that keep_partial didn't make sense with inplace, but hadn't
spent much time understanding that section of the code (took me long
enough to get my head around sender, receiver and match), so I made what
looked like the right change at the time. ;-)
Cheers,
Mark.
Wayne Davison wrote:
On
On Wed, Apr 28, 2004 at 08:38:41AM +1000, Mark Curtis wrote:
> I have written a 'smallish' patch to implement the --inplace option
Looks very promising. I've tweaked it just a bit and committed it in
the patches dir in CVS.
Q: was there a reason you were waiting to reset the keep_partial flag
u
Hi,
Results of a simple performance test on cygwin :
333 files, 30 MB, flat directory, 3 test runs after ramp-up,
Client : cygwin 1.5.9/ssh 3.8p on XP
Server : cygwin 1.5.9/ssh 3.8p on windows 2000 Server (VMWARE)
2.6.0 client to 2.6.0 server : 1 017
Hi,
I have written a 'smallish' patch to implement the --inplace option
as discussed on this mailing list at various points in the past. It
makes a small modification to the sender algorithm so that it won't ask
the receiver to relocate blocks from earlier in the file when running
with the
Just built 2.6.1 and started testing it. Nice job guys. I especially love
the --progress and hardlink tweaks.
Quite often, while I have systems backing up out of cron, I'd love to be
able to see the --progress. Unfortunately, it's just not practical to
crank up the verbosity like that on a regula
On Tue, Apr 27, 2004 at 02:14:10PM -0600, Eric Whiting wrote:
> I was watching the memory usage with a bash command line while loop
> while(true);do cat /proc/$pid/status |grep VmSize ;sleep 60;done
A very nice way to do that. You might want to watch the VmRSS value,
which will tell you how much
Wayne Davison wrote:
>
> On Tue, Apr 27, 2004 at 11:52:11AM -0600, Eric Whiting wrote:
> > ... but here is some representative data:
>
> Thanks for the confirming stats. Some questions/comments:
>
> You didn't mention what command you ran, so I'm curious if the 18M jump
> at the end was due to
On Tue, Apr 27, 2004 at 05:15:25AM -0500, John Van Essen wrote:
> There was a change to rwrite() that seems to be preventing the error
> logging.
Yes, you're right -- 2.6.0 changed this to make more errors go to the
user and fewer to the log file. Neither the old behavior nor the new is
really th
On Tue, Apr 27, 2004 at 09:24:32PM +0300, Sami Farin wrote:
> return value of close() (receiver.c) is ignored.
Thanks! I've checked in a change based on your suggestion. I put the
--fsync option (w/o the -f shortcut) into the patches dir. (Such
changes are part of the initial work for the 2.6.2
On Tue, Apr 27, 2004 at 11:52:11AM -0600, Eric Whiting wrote:
> ... but here is some representative data:
Thanks for the confirming stats. Some questions/comments:
You didn't mention what command you ran, so I'm curious if the 18M jump
at the end was due to using --delete-after? (The way the de
> Those are really nice new options.
Second that! I think this is an awesome feature!
> > [EMAIL PROTECTED]:MM
> > This option allows you to specify at what time to stop rsync, in
> > [EMAIL PROTECTED]:minute numeric format (e.g. [EMAIL PROTECTED]:59).
>
> Is there any reason to
hi.
return value of close() (receiver.c) is ignored.
when running out of quota on NFS (for example),
this can happen (without the patch):
output file(s) is/are truncated to 0 bytes and rsync reports success.
with the fix, this happens:
close "/home/luser/.test.mp3.PwaG50": Disc quota exceeded
rs
Markus,
I am seeing the exact same thing, same two checksums.
The earlier file has size of 511412 and the latter 511395.
Here is the difference:
diff -urN rsync-2.6.1_early/util.c rsync-2.6.1_late/util.c
--- rsync-2.6.1_early/util.c2004-04-22 18:17:15.0 -0400
+++ rsync-2.6.1_late/ut
On Tue, Apr 27, 2004 at 07:34:19PM +0200, Markus W.Weissmann wrote:
> whats going on [with the 2.6.1 tar-file checksums]???
I just made a minor tweak to the tar file and hadn't announced the
change yet. I noticed that a debug fprintf was left in a function
in util.c, and though the statement actu
[EMAIL PROTECTED] wrote:
>
> 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 amoun
Hi folks,
I'm maintaining the darwinports port of rsync and I encountered the
following strange thing:
I updated our port which contains a md5 checksum on 27. April 16:36 GMT.
Then some people had successfull builds (meaning the checksum was
valid). But now its
not anymore, it changed. I had a l
Hi,
I have to parse log file in php script.I want to know exactly file by file if they
were transfered good or if they were an error or if nothing was done.
-- So i've use rsync with the option "-vv" and i can obtain something like this :
delta transmission enabled
send_files failed to open /ho
On Tue 27 Apr 2004, Jon Jensen wrote:
>
> > [EMAIL PROTECTED]:MM
> > This option allows you to specify at what time to stop rsync, in
> > [EMAIL PROTECTED]:minute numeric format (e.g. [EMAIL PROTECTED]:59).
>
> Is there any reason to use a nonstandard date/time format like this?
On Mon 26 Apr 2004, Wayne Davison wrote:
>
> It includes a security note about a fix that affects read/write daemons
> that are not using chroot. If that includes you, you should look into
> upgrading (or maybe enabling chroot on an older rsync).
Is it possible to find the patches responsible fo
On Mon, 26 Apr 2004, Wayne Davison wrote:
> CVS now has an updated time-limit.diff patch in which I simplified the
> code quite a bit and tweaked the options a bit:
Those are really nice new options.
> [EMAIL PROTECTED]:MM
> This option allows you to specify at what time to stop rsync,
Wayne,
Thanks for putting this into the CVS tree. I like your improvements.
-John
On Mon, Apr 26, 2004 at 08:10:50PM -0700, Wayne Davison wrote:
> On Thu, Apr 22, 2004 at 04:20:07PM -0400, John Taylor wrote:
> > Upon a suggestion to improve the --timelimit patch, I have also added
> >
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 t
(As I was composing this, the 2.6.1 release notice on the rsync
list rolled in. The quoted source, below, hasn't changed, so
I'll leave the 'pre-1' references unchanged...)
I have a situation where an error message seems to be sent from
the daemon to the client, but none is logged in the daemon
27 matches
Mail list logo
