On Fri, 21 Jan 2005, Florian Fainelli <[EMAIL PROTECTED]> wrote:
> Hi all
>
> Here is the egrep result :
>
> egrep "SIZEOF|LONGLONG" build_mipsel/rsync-2.6.3/config.h
> /* #undef HAVE_LONGLONG */
> #define SIZEOF_INT 4
> #define SIZEOF_LONG 4
> #define SIZEOF_SHORT 2
>
> and the HAVE_LONGLONG co
Hi,
The following problem has appeared in the past but I have not seen
satisfactory solution.
It is common when synchronizing large amount of files over slow link.
I would like to synchronize 1TB of data between local and remote sites
over WAN.
For the initial synchronization, I would like to t
On Sun, 2005-01-23 12:44:28 +0200, israel Gold <[EMAIL PROTECTED]>
wrote in message <[EMAIL PROTECTED]>:
> The following problem has appeared in the past but I have not seen
> satisfactory solution.
> It is common when synchronizing large amount of files over slow link.
Should work, at least if
This is likely a linux or ssh problem, but perhaps someone else on this
list may have encountered it. I have run about 15,000 instances of
rsync in the last year, (about 500 total hours of rsyncing) using ssh
as a transport mechanism ( actually, I am running the dirvish backup
wrapper, www.dirvi
Hi Wayne,
Thanks - I've enabled logging in my daemons (it's disabled by default)
so hopefully whatever the error is will appear in there shortly.
Regards
Paul
-Original Message-
From: Wayne Davison [mailto:[EMAIL PROTECTED]
Sent: 23 January 2005 07:42
To: Hargreaves, Paul
Cc: rsync@li
It's a local copy so the daemon log isn't showing anything other than:
2005/01/23 11:43:53 [606] rsyncd version 2.6.3 starting, listening on
port 873
I've asked the rsnapshot team how to turn on more diagnostics; it's not
capturing the output of -vvv anywhere.
Thanks
Paul
-Original Messag
On Sun, Jan 23, 2005 at 06:35:13AM -0800, Keith Lofstrom wrote:
> Sometimes in my logs I see, at random, the warning "PRNG is not seeded",
> which some folks encounter when they improperly configure ssh or
> /dev/urandom.
"PRNG" is the Pseudo Random Number Generator, and you are right that it
is u
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 doesn't really
> get used. I looked
Here is what rsync man page states:
-c, --checksum
This forces the sender to checksum all files using a 128-bit MD4
checksum before transfer.
The checksum is then explicitly checked on the receiver and any
files of the same name
which already exist and have the same checksum and
