Hello,
I am a french student and I have written a technical report on an extension of the rsync algorithm to crypted files.I started from the situation of a client machine A user who doesn't wish to save an original file v0 and its successive versions v1 v2 v3 ... on a distant server B but rather
I am currently syncing 1.3 terabytes of files using rsync. This is spread
across about 12 filesystems all on the same server. Unfortunately we are
planning to move away from rsync because it is taking too long to run and it
takes up too much memory (some of the rsync processes take up 1.5 GB
MM == mmikaelfr iso-8859-1
wrote the following on Thu, 27 Jun 2002 15:26:51 +0200 (CEST)
MM I am a french student and I have written a technical report on
MM an extension of the rsync algorithm to crypted files. I started
MM from the situation of a client machine A user who doesn't
What are you moving to?
-Original Message-
From: Granzow, Doug (NCI) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 27, 2002 8:31 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Largest file system being synced
I am currently syncing 1.3 terabytes of files using rsync. This is spread
across
On Tue, Jun 25, 2002 at 05:11:40PM -0400, pyxl wrote:
Well,
Looking at the source for 2.5.5, I'm only seeing mention of it under the
--numeric-ids flag in rsync(1); --owner doesn't make mention of it at all.
What you quoted must be in CVS (I'd look, but I don't know how to do a
remote CVS
We're planning to move to Veritas Volume Replicator. It has the advantage
of working at the filesystem level, so whenever a write is done on the
primary site, the same write is automatically done on the mirror site. For
what I am doing here, it should (hopefully!) work a lot better than rsync
On Thu, Jun 27, 2002 at 03:26:51PM +0200, Mikael moshir wrote:
Hello,
I am a french student and I have written a technical
report on an extension of the rsync algorithm to crypted
files. I started from the situation of a client machine A
user who doesn't wish to save an original file
I haven't gotten it to work successfully, I'm still struggling with the
same setgroups error that you are. However, I can tell you what I have
tried. So far I have rsync configured to run in --daemon mode using the
command: sudo rsync --daemon I can prompt it for a list of modules, but
when I go
On Thu, Jun 27, 2002 at 02:21:08PM -0400, Granzow, Doug (NCI) wrote:
We're planning to move to Veritas Volume Replicator. It has the advantage
of working at the filesystem level, so whenever a write is done on the
primary site, the same write is automatically done on the mirror site. For
On Thu, Jun 27, 2002 at 01:31:12PM -0700, jw schultz wrote:
It doesn't work at the filesystem level. It works at the
block device level. Every time a block is modified it is
queued for transmission to the mirror(s). If the same block
Are there any Linux users out there using the likes of
I am ysyncing text files between NT/95/XP machines and Solaris. I noted
that the text/ascii files created on the windows platforms contain ^M at
the end of each line when transfered to the Solaris system. This can be
explained by the binary transmission and can use FTP is ASCII mode to
prevent
I've got mine setup in inetd.conf to be executed on a per-call request
of port 873 as written in the man pages. The advantage of using this
method, is that when the client is done and disconnects, the daemon
quits, thereby freeing up resources that it was using. Word of warning
though if you want
On Thu, Jun 27, 2002 at 11:30:39AM -0400, Granzow, Doug (NCI) wrote:
I am currently syncing 1.3 terabytes of files using rsync. This is spread
across about 12 filesystems all on the same server. Unfortunately we are
planning to move away from rsync because it is taking too long to run and
Hi Jason,
Are there any Linux users out there using the likes of
RAID'ed-NBD, CODA or
Intermezzo for a similar effect?
The NBD (network block device) looks interesting, it allows
you to mount a remote raw partition - so you can effectively
RAID over the network.
I'd recomend drbd over
Hi...
I am encountering the following error while syncing the data
error message is: "send_files failed to open abcdata1/PABCBTABD.container000
: Value too large to be stored in data type"
Size of the files for which the error is coming are: 31 GB, 35 GB, 40
GB, 52 GB, and 59 GB each.
Please
15 matches
Mail list logo
