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
https://bugzilla.samba.org/show_bug.cgi?id=2106
Summary: Spaces in remote filename
Product: rsync
Version: 2.6.2
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P3
Component: core
On Tue, Nov 30, 2004 at 04:13:18PM -0800, Dan Stromberg wrote:
> If a close were to fail, wouldn't that normally mean that you just
> wouldn't get the last block sync'd out to disk, rather than an entire
> multi-K or multi-M file would be 0 length?
If the disk is full (i.e. out of blocks, but not
On Tue, 2004-11-30 at 12:45 -0800, Wayne Davison wrote:
> On Tue, Nov 30, 2004 at 12:10:05PM -0800, Dan Stromberg wrote:
> > Is there any precedent for rsync creating 0 length files that should've
> > had content in them?
>
> Are you using 2.6.3? Older rsync versions did not check the return of
>
On Thu, Nov 25, 2004 at 06:48:58PM +, Peter Hartley wrote:
> Even better, of course, would be to find out that this sort of operation
> was *already* possible using some rsync features I missed when looking
> into this...
The only way to do this at the moment is to do a local update of an
iden
https://bugzilla.samba.org/show_bug.cgi?id=2104
Summary: Add support for --dry-run with --write-batch
Product: rsync
Version: 2.6.3
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P3
On Fri, Nov 26, 2004 at 12:43:40PM +0100, David Jacoby wrote:
> The best thing was if there was any way to get it in percentage or
> only a list of how many files its going to transfer before the actual
> transfer starts.
Rsync does not determine how many files are going to be transferred
prior to
On Tue, Nov 30, 2004 at 12:10:05PM -0800, Dan Stromberg wrote:
> Is there any precedent for rsync creating 0 length files that should've
> had content in them?
Are you using 2.6.3? Older rsync versions did not check the return of
the close() call, which could result in lost information if a disk
On Tue, Nov 30, 2004 at 01:39:08AM +0800, Dan Jacobson wrote:
> On the man page it says
>-u, --update
> This forces rsync to skip any files for which the destination
> file already exists and has a date later than the source file.
> Mention the case when the d
Is there any precedent for rsync creating 0 length files that should've
had content in them? IE, has anyone ever seen this before?
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 wer
Title: Message
Hi
all,
Could anybody please
suggest the link for downloading the cygwin rsync, which supports
98SE?
Your reply will be
very helpful,
thanks and
rgds
Sanal
Confidentiality Notice
The information contained in this electronic message and any attachments to this
On Tue 30 Nov 2004, Dan Jacobson wrote:
> Paste error:
>--size-only
> Normally rsync will skip any files that are Normally rsync will
This was a patch error in de Debian 2.6.3-1 version that has already
been fixed in the 2.6.3-2 version.
Paul Slootman
--
To unsubscribe o
12 matches
Mail list logo
