"[%d] (%s%s%s) heap statistics:\n",
Could you prepend a newline to the beginning of this so it does not
blend in with the last line of any transfer-related output?
rprintf(FINFO, RSYNC_NAME "\n[%d] (%s%s%s) heap statistics:\n",
Thanks.
--
John Van Essen Un
erpt:'),
! ## 21-Jan-2002 JVE Escape html in text to prevent display problems
! TextArea('fulltext-%d' % id, cgi.escape(text), rows=10, cols=80)])
t.AddCellInfo(row+1, col-1, align='right')
form.AddItem(t)
form.AddItem('')
+ ## 02-May-2002 JVE Add name tag at end
+ form.AddItem('\n\n' % (count+1))
Hope this helps.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
ion more easily.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
3DGamers Systems Software Support <[EMAIL PROTECTED]>
On Sun, 05 Jan 2003, David Garamond <[EMAIL PROTECTED]> wrote:
>just to correct myself: this has nothing to do with rdiff-bac
t have been replaced with a symlink may have the info you need:
- Forwarded message begins here -
From: John Van Essen <[EMAIL PROTECTED]>
Date: Mon, 6 Jan 2003 02:05:47 CST
Subject: Re: directories that change into symlinks
What you need is the --force option. It's not obvious
gument
Since these files are being created on your "FAT32 external HD", something
in these filenames is not allowed on that filesystem. Perhaps the
double-quote and question mark characters are not valid in a filename?
This wold certainly be the case for a Windows system. Thus mkstemp fai
ress (by some clever criterion), then this match either should
> not be done, or the confusing error message should not be printed.
I had submitted a similar bug report and small patch on April 10:
http://lists.samba.org/pipermail/rsync/2003-April/010404.html
There were no followups to it a
t and close
the connection. This can happen if this end has received the file list
from the other end, and is taking too long to generate its own file list
and start any needed file transfers.
The default timeout is zero - meaning no timeout.
Did you use a --timeout argument? Or are you using a dae
to have at least as much free space as the largest file
being transferred.
If the copy fails due to disk full, the temporary will be deleted, and
it may *look* like you have lots of free space after rsync finishes,
wheras you actually ran out of free space while rsync was running.
--
John
ileA and FileB have the same inode in rsync's filelist. FileA may even
no longer exist (that's a risk you take of rsyncing live systems).
Since the inode number are what's used to figure out hardlinks, FileA and
FileB are hardlinked together on the target system.
I have no suggestion for avoiding this pitfall and still use hard links.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
3DGamers Systems Software Support <[EMAIL PROTECTED]>
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
eing cached in memory to
allow the task to complete more quickly - such would be the case with
repeated interactive testing.
> Also, use of more v than -vv can itself cause problems.
True.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
3DGamers Systems Software Support <[EMAIL PROTECTED]>
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
ng one of these (note single vs. double quotes):
'[EMAIL PROTECTED]:/path/band\ -\ album/'
"[EMAIL PROTECTED]:/path/band\\ -\\ album/"
'[EMAIL PROTECTED]:"/path/band - album/"'
"[EMAIL PROTECTED]:'/path/band - album/'"
This mig
, of course, the ones that
> showed up with -v do not state 'up to date', while the others do.
Windows file timestamps have a granularity of 2 seconds instead of 1.
Use --modify-window=1 whenever rsyncing with samba mount filesystems.
--
John Van Essen Univ of MN Alumnus <[
#x27; --exclude '/usr/var/tmp/' --exclude '/usr/var/run/' / /tmp/bkup/ |
>grep -c deleting
> ] 105668
You are using -x, which will not include the contents of any mounted
partitions. 105,668 deletes and no update of the destination makes me
think that /usr on the source is
t times to make it
more accurate which would probably solve your problem. See this
thread in the archives:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg07270.html
A corrected patch is in the next message (7271).
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
ave the userid set to 'nobody' here.
> and my request from the client machine :
>
> rsync -avz--progress -r --ignore-errors --password-file=/etc/rsync-pass
> --exclude-from=/etc/rsync-exclude [EMAIL PROTECTED]::foo_home /home/
>
> Please, help
>
> Francois
--
he function are both available.
What does yours say? The line numbers might be different.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
On Mon, 27 Oct 2003, Tom Holton <[EMAIL PROTECTED]> wrote:
>
> Hi, thanks for the reply. I apologize for not having a
t are variants
of "It's already fixed in CVS".
Are there any particular reasons for holding back the next release?
Will the next release be 2.6.0 because of the protocol number bump?
I'd sure like to see the full list of changes since 2.5.6 and begin
testing a release candidate
invite constructive comments and patches (on
> list) but if someone else wants to pick up the ball and run
> with it i would be pleased to hand it off.
>
> I have formatted it in HTML so if you care it can
> be found at http://www.pegasys.ws/how-rsync-works.html
I think a document such
mend the 2nd:
rsync -av --exclude=/test/dir1/ /foo/test serv2:/foo
rsync -av --exclude=/dir1/ /foo/test/ serv2:/foo/test/
As a matter of habit and principle, I always specify the complete
paths down to the trailing / when I rsync two directories. Then
there's never any confusion about wh
res more in-depth knowledge
of rsync to utilize its various support routines, and I just don't feel
that comfortable with it. So my rsyncs take an extra 20 minutes each
night needlessly transferring hundreds of megabytes of log files. :-/
If anyone else cares to take on this project, be my g
;inode);
}
}
#endif
What happens if the sender, for whatever reason, has no hard link support
compiled in? What will the receiver be reading?
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
decimal place
on the df output? Maybe the source has 3.5 GB _free_, not 3.5 GB used?
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
the -i option
and its argument in rsync's -e option argument:
rsync {options} -e 'ssh -i /path/to/identity' {source} {dest}
I use this form quite frequently in scripts.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change
ch is no longer needed, IMO.
It is very likely that the original logic flaw was found and fixed between
versions 2.4.4 and 2.5.6 (2.5.7 being only a security fix).
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: http://lists.samba.
icial release (hopefully by Christmas)?
Thanks.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
users 29 Dec 16 12:39 a2
-rw-r--r--3 jve users 29 Dec 16 12:39 a3
-rw-r--r-- 5 jve users 29 Dec 16 12:39 a4
-rw-r--r--5 jve users 29 Dec 16 12:39 a5
-rw-r--r--5 jve users 29 Dec 16 12:39 b1
-rw-r--r--5 jve use
; list, which seems unnecessary.
Indeed! It does! Very wasteful. It should only need a list of pointers
to the flist entries and sort that list. Furthermore, with the addition
of the new multiple nodes flag bit requested above, the list of pointers
would only contain pointers to flist entries with that bit set, resulting
in a much smaller list.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
s really needed.
I tried that, and it works just fine.
I used a much larger msleep to begin with so I could do a ps to verify
that the ssh process goes away. It does. So it just needs that little
bit of extra time to do its thang.
--
John Van Essen Univ of MN Alumnus <[
v2.6.0 the default remote shell is ssh instead of rsh. *
* To use previous default of rsh: ./configure --with-rsh=rsh *
********
to make it really clear about the new default.
--
John Van Essen Univ of MN Alumnus
. Note that in your second transfer, where it did have to
resend the file, it was able to match all 8 GB of data and transferred
only a small fraction of that in matching checksum values. Hence a
speedup of 1600+.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
>
newlines
Comments? Suggestions?
Since this doesn't involve executable code, can this get into 2.6.0
(without another "pre" release)?
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: http://lists.samba.org/mailman/
nation as "backenp650:"
And that would indeed be using the home directory on the destination.
Not bad rsync - bad you! ;-)
I would suggest always using --dry-run when debugging scripts like this
and then remove it when it looks like things will work as you intended.
--
John Van
in a day or two after I've tested it.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
On Sat, 3 Jan 2004, Lester Hightower <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I read with interest the mailing list thread found here:
>
> http://marc
st
again, which should succeed and then go on to do the configuration.
But in your case that test fails the second time around (and so on it
recurses, infinitely, rewriting configure.lineno over and over).
Something is apparently wrong either with expr or with bash.
What does the above code look like
On Sun, 4 Jan 2004, jw schultz <[EMAIL PROTECTED]> wrote:
> On Sun, Jan 04, 2004 at 06:35:03AM -0600, John Van Essen wrote:
>> I've modified hlink.c to use a list of file struct pointers instead of
>> copies of the actual file structs themselves, so that will save m
On Sun, 4 Jan 2004 16:23:17 -0800, jw schultz <[EMAIL PROTECTED]> wrote:
> On Sun, Jan 04, 2004 at 05:30:03AM -0800, jw schultz wrote:
>> On Sun, Jan 04, 2004 at 06:35:03AM -0600, John Van Essen wrote:
>> > I've modified hlink.c to use a list of file struct pointers
e skipped since they are hardlinked later.
The final walk-through that creates the hardlinks for the
non-head files can walk the qsorted list and use the head
pointer as the target for the hardlinks of the non-nead files.
No extra memory required beyond that already required for the
qsorted pointer
On Mon, 5 Jan 2004 19:09:23 -0800, jw schultz <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 05, 2004 at 01:44:37AM -0600, John Van Essen wrote:
>> I did that differently (and more simply, I think). Changed only one line
>> and added two lines:
>>
>> @@ -24,8
On Tue, 6 Jan 2004 15:11:54 -0800, jw schultz <[EMAIL PROTECTED]> wrote:
> On Tue, Jan 06, 2004 at 02:04:19AM -0600, John Van Essen wrote:
>> On Mon, 5 Jan 2004, jw schultz <[EMAIL PROTECTED]> wrote:
> [snip]
>> > union links {
>> > struct
onsistently. So the final
comparison can be done on the addresses of the file_structs,
since they are not moved around and will remain constant:
return ( ( f1 < f2 ) ? -1 : ( f1 > f2 ) );
(Unsure if the code is right, but you get my drift.)
For filesets with many hardlinks, this w
I haven't coded anything pending review of this bug by whoever
coded the IOERR_VANISHED feature to verify my analysis. (Wayne?)
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo
On Wed, 7 Jan 2004 00:03:13 -0800, jw schultz <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 07, 2004 at 01:04:34AM -0600, John Van Essen wrote:
>>
>> Right. You've just explained the here-to-fore unknown reason
>> why that sibling hlinking was being done in a separate
ructure when --hard-links is not used).
Shall we take the coding details discussion off-list? I imagine
that the faithful readers of this mailing list are getting a bit
weary reading about this fairly obscure bit of code...
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
-
job, so I will have very little
free time (certainly not enough for anything substantial here)
> I don't want to duplicate the work that others would enjoy doing, so
> feel free to let me know if you start on something.
Can I feel free to let you know you can do it all? And I will go
On Tue, 13 Jan 2004, Wayne Davison <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 07, 2004 at 02:11:35AM -0600, John Van Essen wrote:
>> But if the client is local and the server is remote, IOERR_VANISHED
>> gets set on the remote server, but is never passed to the local
>> cl
On Tue, 13 Jan 2004 20:47:30 -0800, Wayne Davison <[EMAIL PROTECTED]> wrote:
> On Tue, Jan 13, 2004 at 10:38:23PM -0600, John Van Essen wrote:
>> Are you by any chance doing internal rsyncs?
>
> No. What remote shell are you using? If it doesn't propagate the exit
&
On Thu, 15 Jan 2004, Wayne Davison <[EMAIL PROTECTED]> wrote:
> On Tue, Jan 13, 2004 at 11:45:22PM -0600, John Van Essen wrote:
>> But as I mentioned, it also happens with a daemon
>
> Yeah, the daemon's exit code is not available to the client, so it is
> getting
and set IOERR_VANISHED?
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
d does, for me).
>>
>
> Hello!
>
> Thank you!
> It works :-)
Another happy Cygwin user. :)
Since this has been such a long-standing, important bug and is
finally now fixed, maybe the contents of that message announcing
the 1.5.6-1 cygwin dll deserves placement on the rsyn
On Thu, 26 Feb 2004, andrew <[EMAIL PROTECTED]> wrote:
>
> Paul Slootman wrote:
>> On Wed 25 Feb 2004, andrew wrote:
>>
>>>rsync -av --exclude "/user/profile/" --delete /home/user [EMAIL PROTECTED]:/home
>>>
>>>This works as I expect, sender:/home/user/profile/ is not copied, except
>>>that recei
On Wed, 10 Mar 2004, Wayne Davison <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 10, 2004 at 01:11:35PM -0500, D Andrew Reynhout wrote:
>> but I'm less clear on
>> why (it appears) that *both* sides sort the flist.
>
> This is because the flist gets sent as it is created, so it is sent
> unsorted. Wit
pattern: /foo/bar (note missing 'me')
Source file: /home/me/foo/bar
Target file: /dest/foo/bar (note missing 'me')
Example cmd: rsync -a --relative /home/me /dest
Source root: /home
Target root: /dest
I/E pattern: /home/me/foo/bar (note full path)
a --dry-run first to determine the names
of the pdf files. Grep the -v output of rsync for '\.pdf$', store
that list in a file, then do a real run with the files-from option.
I didn't try this - so I haven't verified that this will work.
--
John Van Essen Univ of MN
On Tue, 30 Mar 2004, Wayne Davison <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 19, 2004 at 03:21:16AM -0600, John Van Essen wrote:
>> In make_file(), when readlink_stat() fails, if error is NOENT
>> then perhaps do the same that that send_files() now does and
>>
r root, not the
filesystem root or partition root.
The source transfer root is the source path with any trailing
node removed up to the last slash. If the source path *ends*
with a slash, then nothing is removed and the source path
*is* the transfer root.
--
John Van Essen Univ of MN Alumnus
(avoiding
Copy on Write) after the client forks the generator, thus using
less memory in systems that support CoW.
I think this (perhaps reworded :D) is worth noting in the INTERNAL
section.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or chan
g our heads about...
So ignoring all the 04/20 errors, brings us to the 04/21 errors.
The ones at 04:30 looks like a minor shutdown problem that didn't
affect the transfer.
The one at 08:00 is from the kill.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
problem that is as obscure as this one is... :)
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
backup.
I think Brian's very simple patch (refined version posted 5/11)
using an extra set_modtime() arg and testing for make_backup is
the right fix. That fix could be refined even further by also
checking for any specified backup-dir. If one was given, then
it will be OK to always restore m
I posted a comment to bug 4402 a few days ago and it never appeared
on the rsync mailing list. In the past, bugzilla posts automatically
got emailed to the rsync list.
The mailing list archive shows that the last message from bugzilla
was received by the mailing list on Feb 25. Since then, these
On Wed, 5 Sep 2007, Matt McCutchen <[EMAIL PROTECTED]> wrote:
> On 9/5/07, Martin Schr�der <[EMAIL PROTECTED]> wrote:
>> That didn't stop the asian spam... :-(
>
> I guess the sender of that spam subscribed to the list first?
> Requiring a captcha for subscription may stop it from happening again.
ot;
messages actually help pinpoint directories whose contents should be
excluded, in this case via --exclude=/drbd/var/www/tmp/*
Also, if you want, you can also check the exit code within a script and
treat value 24 the same as a 0 (e.g. no extra warnings about failure).
John Van Essen
--
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 Thu, 27 Mar 2008, Reeve Yang <[EMAIL PROTECTED]> wrote:
> Does "bwlimit" option really work on rsync locally?
Yes, it does.
> rsync without --bwlimit:
>> iostat; rsync -a -r --stats swapfile swapfile.rsync; iostat
> sent 2147745923 bytes received 42 bytes 23472633.50 bytes/sec
> ry
On Fri, 28 Mar 2008, Reeve Yang <[EMAIL PROTECTED]> wrote:
> Is there anyway to make rsync use direct I/O bypassing FS buffer?
I'm not an expert on that by any means, but AFAIK, rsync supports that
only via this patch:
http://rsync.samba.org/ftp/rsync/patches/drop-cache.diff
(You'll have to co
here than just adding back a "!am_daemon" test?
Also - I'd sure like to see a message in the rsyncd log when the
file list transfer has been completed. That would help determine
at what stage things are failing (and how long it took for the
file transfer to complete, in case th
y be related to this bullet item
in the NEWS file:
* Changed hardlink info and file_struct + strings to use
allocation pools. This reduces memory use for large file-
sets and permits freeing memory to the OS. (J.W. Schultz)
Wayne? JW? Any thoughts?
--
John Van Esse
var/local/backups/latest 192.168.0.1:/var/local/backups/latest/
Unchanged content won't be disturbed. Changed or new content will
get transferred.
When that completes successfully, then do the second rsync, but
do *not* use --delete-excluded. The second rsync should include
latest a
d to Z.
3. If A (and B and Z) change and remain hardlinked, the new content
will be transferred, A and B will be hardlinked, and the hardlink
with Z is now lost because rsync doesn't know anything about it.
Z on the target now contains old content and becomes independent.
--
J
at this was possible. It seems this also
works for non-daemon mode as long as you specify the full paths, I
believe (or use paths relative to the remote user's home directory).
Can you please add examples of this to the man page Usage section?
--
John Van Essen Univ of MN Alumnus <
full_fname(fname), strerror(errno));
exit_cleanup(RERR_FILEIO);
}
Wayne - why is the "write failed" message not being displayed?
It should have contained the EFBIG File Too Large error message.
That would helped figure out the original problem (whi
hould have been deleted will now be deleted.
So the documentation for --keep-dirlinks should warn that also using
-x (--one-file-system) has a side effect where symlinked directories
followed by --keep-dirlinks that reside on another file system will
not be processed for deletions.
--
John
)
The email address in <...> is the one used to send the email to you.
Then you can use the mailman webpage for rsync (see the footer of this
email) to get a password reminder emailed to you using that address.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To
llowing command line:
>
> rsync -avz --bwlimit=5000 /extra/pub/ 192.168.1.73::pub
To preserve hardlinks, you need to include the -H option (it's
not implied in the -a option).
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change op
file that is included in the file list has been removed by
the time the file metadata compare operation is performed.
You are going to have to diagnose the other two problems by looking
at the two paths in question.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
d at least 60 seconds have elapsed since
the last keep-alive?
Also - as an optimization, if a --timeout value has been given then
use 1/2 of that value for the keep-alive interval (instead of 60).
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change
On Tue, 30 Nov 2004, Dan Stromberg <[EMAIL PROTECTED]> wrote:
>
> We were doing a roughly 1 terabyte transfer, and upon running a python
> script to verify the integrity of the transfer, we discovered a small
> number of files that were 0 length, that shouldn't have been, all in the
> same user's
On Wed, 8 Dec 2004, Grant Carmichael <[EMAIL PROTECTED]> wrote:
>
> With a non root user, ssh will authenticate them, but then the rsync
> process dies.
...
> My config file looks like:
>
> uid = nobody
> gid = nobody
> use chroot = no
> max connections = 5
> syslog facility = local5
On Sun, 19 Dec 2004, <[EMAIL PROTECTED]> wrote:
> source vs destination in bytes
> -
> a) 20480 vs 34922496
> b) 28672 vs 24576
> c) 61718528 vs 61714432
> d) 157790208 vs 157786112
>
> each directory consists of subdirectories of medical images in dicom format.
> Most inte
to make them relative.
Suggestion to Wayne - this security functionality could be described
in its own "Security Issues" or "Daemon vs. non-daemon operation"
section on the manpage rather than buried within an option description.
--
John Van Essen Univ of MN Alumnu
Wayne,
> diff -u -r1.1.1.6 rsync.c
> --- rsync.c 3 Jan 2004 11:22:00 - 1.1.1.6
> +++ rsync.c 21 Dec 2004 12:04:56 -
> @@ -260,7 +260,7 @@
> change to groups that the user is a member of */
> change_gid = is_in_group(file->gid);
>
ectory of the login user and define paths
for the above files that are writable by that user.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
ess via ssh? Some configs disable that.
Lastly - what version of rsync are you using (always important to know).
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
receiver is still alive and the sender
should reset its timeout timer.
I run into this problem quite often when trying to sync large archives
with sparse updates to a very busy, disk I/O intensive server (exactly
the conditions you described).
--
John Van Essen Univ of MN Alumnus <[EMAI
sing a root directory for a target can be very dangerous if
you later add --delete and don't get things quite right.
I strongly suggest always using --dry-run (or -n) to test things out.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
g.log for long long to see why
the test for it failed. Does your cross compiler really not have it?
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
the same name in the working directory, append a " .":
rsync -tv rsync.dsbl.org::dsbl/rbldns-fresh-list.dsbl.org .
Hope that helps. Worked for me.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: https://lists.samba.org/m
t seems to be the case here.
Try this. In config.h, replace:
/* #undef HAVE_LONGLONG */
with
#define HAVE_LONGLONG 1
and try compiling again. If your cross-compiler doesn't have this
feature and you get compilation errors and you can't fix them, then
put them in a reply here and we&#x
On Thu, 20 Jan 2005, Wayne Davison <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 20, 2005 at 01:54:20AM -0600, John Van Essen wrote:
>> (Note to Wayne - isn't it dangerous to assume that off_t is 64 bits?
>
> Yeah, it probably is -- that code was always a kluge that doe
vior (when it's not a security fix) can be
upsetting to those who depend upon it.
But if nobody on this list sees any problem with that, then go for it.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: https://lists.samba.org/mailman/lis
ting to
a directory, it will be treated as matching a
directory from the sender.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, re
e your out-of-memory problem. Use with --dry-run, first,
to see how things go.
--
John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
ne.)
If the machines use different timezones, put TZ=GMT before the find:
TZ=GMT find /mailhome -ls | sort +10 >/tmp/serverN.txt
so all the timestamps will be the same.
Then use rsync to gather them on one machine and do diffs between them.
--
John Van Essen Univ of Minn. Alum
live? It requires the generator to occasionally
send a NOP to the sender so that the sender resets its timeout timer.
There's a bugzilla item on this:
https://bugzilla.samba.org/show_bug.cgi?id=1889
I think this should be enabled by default, with a --no-keep-alive option
to disable it if s
namic one. Just a guess...
The first rsync to delete the directory is successful because since it
does no file transfers, no compression is needed.
--
John Van Essen Univ of Minn. Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
/archive/trouble I believe).
What does the backtrace output from gdb show?
I'm mystified why this error does not happen on your other rsync that
transfers an empty directory... What does an strace for that show that
is different from this one, I wonder?
--
John Van Essen Univ of
y is
the default initial rule. I've never seen anyone using this...
Have you tried the rsync without it? The "/" could be interpreted in
two ways - as the explicit top-level root directory, or as a trailing
slash on a null directory, which rsync might treat the same as a "
*). That way, there's no wildcard expansion
because no filenames will match that combined pattern.
Maybe all man page examples should use the '=' format?
--
John Van Essen Univ of Minn. Alumnus <[EMAIL PROTECTED]>
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
hem to
see what's going on.
> How can see with rsync more details of the transfers ,
>
> y try to use rsync -avvz but is the = rsync -avz, i
> want see more details, how can i do?
They shouldn't be the same...
Using more v's is the right thing to do.
these supposed to be resolved when the program
is initially loaded at run-time?
This has not been a problem in the past, AFAIK.
Perhaps some newer library is trying to be too clever for its own good.
As a workaround, maybe rsync could do a call to getpwuid() and getgrgid()
before doing the ch
l fails, then please include:
- Current listing of rsyncd.conf (you're obviously no longer
using /tmp if you've been futzing with its permissions...)
- output of ls -la for the receiving directory
--
John Van Essen Univ of Minn. Alumnus <[EMAIL PROTECTED]>
1 - 100 of 151 matches
Mail list logo
