On Tue, Feb 10, 2004 at 01:40:48PM +0900, Shinichi Maruyama wrote:
> I tried rsync 2.6.1cvs on my FreeBSD 4.X boxes.
> It dumps core when preserve_hard_links and backup.
> And SUPPORT_HARD_LINKS is true.
>
> rsync -avH --delete --backup --backup-dir=/some/backup/dir \
>
I tried rsync 2.6.1cvs on my FreeBSD 4.X boxes.
It dumps core when preserve_hard_links and backup.
And SUPPORT_HARD_LINKS is true.
rsync -avH --delete --backup --backup-dir=/some/backup/dir \
srchost::dir/ dir/
The core says...
On Thu, Feb 05, 2004 at 09:27:51PM -0800, jw schultz wrote:
> As those of you who watch CVS will be aware Wayne has been
> making progress in reducing memory requirements of rsync.
> Much of what he has done has been the product of discussions
> between he and myself that started a month ago with J
On Tue, Feb 10, 2004 at 10:11:09AM +1100, Donovan Baarda wrote:
> On Tue, 2004-02-10 at 07:48, Jason M. Felice wrote:
> > This patch adds the --link-by-hash=DIR option, which hard links received
> > files in a link farm arranged by MD4 file hash. The result is that the system
> > will only store o
On Tue, 2004-02-10 at 07:48, Jason M. Felice wrote:
> This patch adds the --link-by-hash=DIR option, which hard links received
> files in a link farm arranged by MD4 file hash. The result is that the system
> will only store one copy of the unique contents of each file, regardless of
> the file's
This patch adds the --link-by-hash=DIR option, which hard links received
files in a link farm arranged by MD4 file hash. The result is that the system
will only store one copy of the unique contents of each file, regardless of
the file's name.
Anyone have an example of an MD4 collision so I can t
On Mon, Feb 09, 2004 at 09:14:06AM -0500, Jason M. Felice wrote:
> I got the go-ahead from the client on my --link-by-hash proposal, and
> the seed is making the hash unstable. I can't figure out why the seed
> is there so I don't know whether to cirumvent it in my particular case
> or calculate a
here is the output of what I get:
rsync: error writing 16385 unbuffered bytes - exiting:
Broken pipe
rsync error: error in rsync protocol data stream (code
12) at io.c(463)
rsync version is: rsync version 2.5.5 protocol
version 26
why does rsync fail, what has to happen for this error
code to
I don't read the russian, sorry...
Andrzej Filip wrote:
NOC (FMC) wrote:
Verification F. Steerage wrote:
[...]
> In english, please ...
> Francois
>
Do you really want to read english translation of this spam in russian ?
--
FMC Network Operations Center Luxembourg
E-mail [EMAIL PROTE
NOC (FMC) wrote:
Verification F. Steerage wrote:
[...]
> In english, please ...
> Francois
>
Do you really want to read english translation of this spam in russian ?
--
Andrzej [en:Andrew] Adam Filip http://anfi.freeshell.org backup: [EMAIL PROTECTED]
--
To unsubscribe or change options: http://lis
In english, please ...
Francois
Verification F. Steerage wrote:
Быстрая раскрутка и эффективная рекламная поддержка Вашего бизнеса:
Быстрый результат!
Сегодня Вы можете выбрать удобный и действенный вариант продвижения
товаров или услуг Вашей компании посредством RuNet'a. Это -
единовреме
Wich Unix use you ?
Francois
Tarun Karra wrote:
HI,
My name is tarun and iam new to this list..
Can any one please help me ??
How can i kill a rsync.. Suppose if iam in middle of rsync of a whole 10gb of data. Can i kill rsync in the middle using kill "rsync process id" and resume it later, wou
What is the point to checksum_seed? When reading/writing batch, it is
initialized to a constant value, otherwise it is initialized to
time(NULL). It certainly has no useful cryptographic value :)
I got the go-ahead from the client on my --link-by-hash proposal, and the
seed is making the hash un
13 matches
Mail list logo
