Michael Best wrote:
I ask because a client had a broken filesystem that occasionally has 2T+
files on it (broken filesystem, so they weren't actually that big) but
we happily ran up a huge b/w bill with rsync.
For this specific example you could probably wildcard match the files with a
Shachar-
True enough - with one
additional thought - if the block size is
set to be the square root of the file size,
then the load factor on the hash table becomes
dynamic in and of itself (bigger block size
= less master table entries = fewer hash
collisions).
In the case of
On Tue, Mar 01, 2005 at 04:44:07PM +0100, Paul Slootman wrote:
- the old -c, --checksum line hasn't been removed.
- there's a -C without enclosing \fB and \fP
Thanks -- I've checked in fixes for these.
- you replaced behaviour with behavior. I prefer the former (having
been to an
On Tue, Mar 01, 2005 at 09:34:02AM -0800, Wayne Davison wrote:
The period is part of what is output (to make them all 4 characters
wide).
The other string choice I considered was using delt instead of del..
Maybe that would be better?
..wayne..
--
To unsubscribe or change options:
This is less a question about rsync and more about how rsync can be used as
a backup solution in a particular case. If one of the tools built over
rsync for this purpose solves this, I'm eager to hear how. Otherwise,
suggestions are welcome.
Server-initiated backups are easy. The rsync
On 2005-03-01 16:26:56 -0500, Andrew Gideon wrote:
So is there a way around this? I was thinking about having the client run a
program on the backup server which causes the usual server-initiated backup
to occur. But how would this work if the laptop is behind a NAT device?
Use ssh (with
https://bugzilla.samba.org/show_bug.cgi?id=2403
Summary: ssh port setting
Product: rsync
Version: 2.6.4
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P3
Component: core
https://bugzilla.samba.org/show_bug.cgi?id=2403
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Tue, Mar 01, 2005 at 03:53:45PM -0800, Josh Smith wrote:
The problem when away if I turned off chroot, or if I put a copy of
libnss_ldap.so.2 into ${path}/lib/libnss_ldap.so.2.
Some folks have been reporting that an rsync daemon running on FC 2 (and
now FC 3) with chroot enabled dies when
WD == Wayne Davison [EMAIL PROTECTED]
WD The most useful thing would be for someone to get a core dump of the
WD crash, list the backtrace, and discover if this is a bug in the
WD libraries. If (as I suspect) it is, a bug report to the affected
WD library's author is in order.
Let me know if I
rsync commandline:
/usr/bin/rsync -e /usr/bin/ssh --archive --compress --sparse
--verbose --stats --delete --numeric-ids --partial --relative
--one-file-system target.host:/ /destination/path/
target rsync version: 2.6.3
destination rsync version: 2.6.2
The server we're trying to
Date: Tue Mar 1 17:28:46 2005
Author: wayned
Update of /data/cvs/rsync
In directory dp.samba.org:/tmp/cvs-serv18514
Modified Files:
rsync.yo rsync.1
Log Message:
Fixed two glitches Paul pointed out.
Revisions:
rsync.yo1.254 = 1.255
Date: Tue Mar 1 19:42:31 2005
Author: wayned
Update of /data/cvs/rsync
In directory dp.samba.org:/tmp/cvs-serv24999
Modified Files:
generator.c
Log Message:
Made the multi-FOO-dest loop a little nicer.
Revisions:
generator.c 1.164 = 1.165
Date: Tue Mar 1 23:02:23 2005
Author: wayned
Update of /data/cvs/rsync
In directory dp.samba.org:/tmp/cvs-serv14525
Modified Files:
rsync.yo rsync.1
Log Message:
Improved the description of --rsync-path.
Revisions:
rsync.yo1.255 = 1.256
Date: Wed Mar 2 01:48:25 2005
Author: wayned
Update of /data/cvs/rsync
In directory dp.samba.org:/tmp/cvs-serv27163
Modified Files:
rsyncd.conf.yo rsyncd.conf.5
Log Message:
Mention that specifying /dir/** is a safer way than /dir/
alone to ensure that files inside a dir are fully
15 matches
Mail list logo
