https://bugzilla.samba.org/show_bug.cgi?id=3492
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from [EM
https://bugzilla.samba.org/show_bug.cgi?id=3488
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3492
Summary: rsync: connection unexpectedly closed (24 bytes read so
far)
Product: rsync
Version: 2.6.7
Platform: Other
OS/Version: HP-UX
Status: NEW
Severity: n
https://bugzilla.samba.org/show_bug.cgi?id=3491
--- Comment #1 from [EMAIL PROTECTED] 2006-02-08 02:22 MST ---
I like this idea. I, too, have seen degradation in response times when rsync
starts on a large hierarchy. Using nice didn't help (much).
Wouldn't it be better to count up
https://bugzilla.samba.org/show_bug.cgi?id=3491
Summary: throttle disk IO during filelist/directory parsing
Product: rsync
Version: 2.6.4
Platform: All
URL: http://vilius.multiply.com/video/item/10
OS/Version: Linux
Stat
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #4 from [EMAIL PROTECTED] 2006-02-07 07:25 MST ---
There is now a patch named detect_renamed.diff in the patches dir that
implements the basics of finding renamed files. This will probably go onto the
trunk for the release a
https://bugzilla.samba.org/show_bug.cgi?id=3299
--- Comment #3 from [EMAIL PROTECTED] 2006-02-07 05:33 MST ---
I should also mention that there is now an option that tells rsync that you
want it to pass through all high-bit characers unescaped (instead of trying to
escape only the inv
https://bugzilla.samba.org/show_bug.cgi?id=3488
--- Comment #3 from [EMAIL PROTECTED] 2006-02-06 15:09 MST ---
>I'm assuming by "hung" you mean more of a "hang up", as in problem-causing item
>where rsync died, rather than "hung" as in the process keeps running but stops
>doing anyth
https://bugzilla.samba.org/show_bug.cgi?id=3488
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from [EM
https://bugzilla.samba.org/show_bug.cgi?id=3485
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #3 from [EM
https://bugzilla.samba.org/show_bug.cgi?id=3488
--- Comment #1 from [EMAIL PROTECTED] 2006-02-06 12:23 MST ---
Created an attachment (id=1722)
--> (https://bugzilla.samba.org/attachment.cgi?id=1722&action=view)
Truss output.
--
Configure bugmail: https://bugzilla.samba.org/userpre
https://bugzilla.samba.org/show_bug.cgi?id=3488
Summary: writefd_unbuffered failed to write 4096 bytes: phase
"unknown" [generator]: Broken pipe (32)
Product: rsync
Version: 2.6.6
Platform: Sparc
OS/Version: Solaris
https://bugzilla.samba.org/show_bug.cgi?id=3299
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3485
--- Comment #2 from [EMAIL PROTECTED] 2006-02-06 04:21 MST ---
(In reply to comment #1)
> Does the source tree contains hard-linked files?
> If so, has -H rsync option been used?
> cp -a would preserve hard links.
>
Yes, the command wa
https://bugzilla.samba.org/show_bug.cgi?id=3485
--- Comment #1 from [EMAIL PROTECTED] 2006-02-05 13:05 MST ---
Does the source tree contains hard-linked files?
If so, has -H rsync option been used?
cp -a would preserve hard links.
--
Configure bugmail: https://bugzilla.samba.org/us
https://bugzilla.samba.org/show_bug.cgi?id=3485
Summary: rsync uses more space in destination even with -S
specified
Product: rsync
Version: 2.6.6
Platform: x86
OS/Version: Linux
Status: NEW
Severity: majo
https://bugzilla.samba.org/show_bug.cgi?id=2793
--- Comment #1 from [EMAIL PROTECTED] 2006-02-04 21:09 MST ---
I can't reproduce this with CVS rsync. I made test_pierre/test.file with the
given attributes and values. When I made a copy of test_pierre, the attributes
were synchronize
https://bugzilla.samba.org/show_bug.cgi?id=3304
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3479
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|normal |enhancement
Status|NEW
https://bugzilla.samba.org/show_bug.cgi?id=3479
Summary: Request: timestamps in --log-format
Product: rsync
Version: 2.6.7
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Compone
https://bugzilla.samba.org/show_bug.cgi?id=2570
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3241
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3147
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=2499
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3271
--- Comment #11 from [EMAIL PROTECTED] 2006-02-01 12:53 MST ---
Sorry for forgetting to get back to this bug for so long. I've finally
analyzed the strace output, and it shows that the generator received an error
about the socket closin
https://bugzilla.samba.org/show_bug.cgi?id=3444
--- Comment #5 from [EMAIL PROTECTED] 2006-02-01 02:46 MST ---
--ignore-case solves the critical problem of unwanted file deletions.
There still is a (less critical) problem when one want to change the case of a
file name. Even on case
https://bugzilla.samba.org/show_bug.cgi?id=3465
--- Comment #3 from [EMAIL PROTECTED] 2006-01-31 11:13 MST ---
(In reply to comment #2)
> Another work around might be to allow a --max-size of zero combined with a
> --delete.
The recommended way to ask rsync to only delete files is to
https://bugzilla.samba.org/show_bug.cgi?id=3461
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3444
--- Comment #4 from [EMAIL PROTECTED] 2006-01-31 10:34 MST ---
(In reply to comment #3)
> Do you mean that the ignore-case.diff patch that is found in the patches
> directory of the 2.6.6 source distribution does not work ?
That's right
https://bugzilla.samba.org/show_bug.cgi?id=3465
--- Comment #2 from [EMAIL PROTECTED] 2006-01-31 09:13 MST ---
Another work around might be to allow a --max-size of zero combined with a
--delete. --maxsize of zero is not supported in rsync. While it wouldn't
completely solve the origi
https://bugzilla.samba.org/show_bug.cgi?id=3444
--- Comment #3 from [EMAIL PROTECTED] 2006-01-31 08:16 MST ---
> Note that the patch that came
> with 2.6.6 builds, but is ineffective. The version in CVS should be OK.
Do you mean that the ignore-case.diff patch that is found in the pa
https://bugzilla.samba.org/show_bug.cgi?id=3277
--- Comment #9 from [EMAIL PROTECTED] 2006-01-30 16:31 MST ---
I'm sorry for abusing your Bugzilla. Let the discussion continue on the
mailing list if necessary. Never mind changing the behavior of -a, but an
official alias for -rltE -
https://bugzilla.samba.org/show_bug.cgi?id=3465
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|normal |enhancement
Status|NEW
https://bugzilla.samba.org/show_bug.cgi?id=3465
Summary: --files-from does not --delete
Product: rsync
Version: 2.6.6
Platform: Other
OS/Version: AIX
Status: NEW
Severity: normal
Priority: P3
Component: cor
https://bugzilla.samba.org/show_bug.cgi?id=3277
--- Comment #8 from [EMAIL PROTECTED] 2006-01-30 15:12 MST ---
This is not really the place to hold a tangent conversatation, but no, I don't
want behavior #2, as I'm not running as root (but I do have multiple groups
associated with my
https://bugzilla.samba.org/show_bug.cgi?id=3277
--- Comment #7 from [EMAIL PROTECTED] 2006-01-30 14:36 MST ---
(In reply to comment #6)
> Yes -- I would. I do a lot of copying where I want the permissions and groups
> copied exactly from the source.
If you care about the permissions
https://bugzilla.samba.org/show_bug.cgi?id=3277
--- Comment #6 from [EMAIL PROTECTED] 2006-01-30 11:56 MST ---
(In reply to comment #5)
> In fact, would anyone object if the non-root meaning of -a changed
> to behavior #3?
Yes -- I would. I do a lot of copying where I want the perm
https://bugzilla.samba.org/show_bug.cgi?id=3461
--- Comment #7 from [EMAIL PROTECTED] 2006-01-29 14:17 MST ---
(In reply to comment #6)
> The traditional use of --temp-dir (I think) is for situations when the
> receiving partition does not have enough free space to accomodate a tempor
https://bugzilla.samba.org/show_bug.cgi?id=3277
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Comment #5
https://bugzilla.samba.org/show_bug.cgi?id=3461
--- Comment #6 from [EMAIL PROTECTED] 2006-01-29 03:30 MST ---
The traditional use of --temp-dir (I think) is for situations when the
receiving partition does not have enough free space to accomodate a temporary
copy of a large file. Th
https://bugzilla.samba.org/show_bug.cgi?id=3461
--- Comment #5 from [EMAIL PROTECTED] 2006-01-29 02:04 MST ---
Created an attachment (id=1712)
--> (https://bugzilla.samba.org/attachment.cgi?id=1712&action=view)
Make the --partial-dir get used when copying
As mentioned, if --temp-dir
https://bugzilla.samba.org/show_bug.cgi?id=3461
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #4 from [EM
https://bugzilla.samba.org/show_bug.cgi?id=2240
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3430
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3277
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|normal |enhancement
Status|ASSIGNED
https://bugzilla.samba.org/show_bug.cgi?id=2868
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3444
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|critical|enhancement
Status|NEW
https://bugzilla.samba.org/show_bug.cgi?id=3461
--- Comment #3 from [EMAIL PROTECTED] 2006-01-28 18:27 MST ---
Hmmm. It's true that rsync interleaves memory-mapped reads from the basis file
and writes to the temporary file. A smart disk scheduler should avoid making
the head dart ba
https://bugzilla.samba.org/show_bug.cgi?id=3461
--- Comment #2 from [EMAIL PROTECTED] 2006-01-28 16:45 MST ---
I was a bit unclear, it's not that it's just a different device, it's a
different physical disk.
For a dataset of about 45GB we see an rsync time of about 2 hrs. When we use
https://bugzilla.samba.org/show_bug.cgi?id=3461
--- Comment #1 from [EMAIL PROTECTED] 2006-01-28 14:19 MST ---
I don't see how using a --temp-dir on a different device could make the
transfer faster, if indeed it does. At some point, all of the data of file.dat
must go from memory to
https://bugzilla.samba.org/show_bug.cgi?id=3461
Summary: rsync is not atomic when temp-dir is on different device
Product: rsync
Version: 2.6.7
Platform: Other
OS/Version: Linux
Status: NEW
Severity: enhancement
Pri
https://bugzilla.samba.org/show_bug.cgi?id=3444
--- Comment #1 from [EMAIL PROTECTED] 2006-01-25 16:38 MST ---
It's pretty clear that the trouble is the case insensitivity of the filesystem.
In fact, I reproduced this behavior on a vfat partition mounted on Linux:
mkdir test1 tes
https://bugzilla.samba.org/show_bug.cgi?id=3444
Summary: Cygwin files trashed when they only differ in the case
of the name
Product: rsync
Version: 2.6.6
Platform: x86
OS/Version: Windows XP
Status: NEW
Se
https://bugzilla.samba.org/show_bug.cgi?id=3432
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3432
--- Comment #1 from [EMAIL PROTECTED] 2006-01-21 14:26 MST ---
--cvs-ignore ignores both that laundry list in exclude.c and any additional
files specified in per-directory .cvsignore files. I downloaded the package
you linked and found
https://bugzilla.samba.org/show_bug.cgi?id=3432
Summary: rsync -azv --cvs-exclude forgets "LocalSettings.php"
Product: rsync
Version: 2.6.6
Platform: x86
URL: http://pto.linux.dk/albackup.tgz
OS/Version: Linux
Status: NE
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #8 from [EMAIL PROTECTED] 2006-01-21 13:35 MST ---
Created an attachment (id=1705)
--> (https://bugzilla.samba.org/attachment.cgi?id=1705&action=view)
Suggested changes to man page for --one-file-system
Wayne seems to have
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #7 from [EMAIL PROTECTED] 2006-01-21 09:16 MST ---
AFAIK, other tools that have a don't-traverse-file-systems option (find, du,
..) in the unix world ignore the mount point (as it logically belongs to the
fs you don't want to
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #6 from [EMAIL PROTECTED] 2006-01-20 15:03 MST ---
Created an attachment (id=1704)
--> (https://bugzilla.samba.org/attachment.cgi?id=1704&action=view)
Makes -x -x exclude mount points themselves
This patch should do it. Ve
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #5 from [EMAIL PROTECTED] 2006-01-20 13:43 MST ---
(In reply to comment #4)
> We could make this user-selectable by letting the user repeat the -x option to
> choose to eliminate the mount-point dirs from the transfer.
In fa
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #4 from [EMAIL PROTECTED] 2006-01-20 13:02 MST ---
I know of no way to find the attributes of the underlying mount-point directory
when the mount is present. And leaving out the mount-point dir is not an
improvement in my bo
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #3 from [EMAIL PROTECTED] 2006-01-20 11:57 MST ---
(In reply to comment #2)
> No, we copy the mount-point directory on purpose because we want it to be
> there
> should the remote system need to mount their own filesystem at
https://bugzilla.samba.org/show_bug.cgi?id=2790
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Comment #4
https://bugzilla.samba.org/show_bug.cgi?id=3362
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3430
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from [EM
https://bugzilla.samba.org/show_bug.cgi?id=3430
--- Comment #1 from [EMAIL PROTECTED] 2006-01-20 10:06 MST ---
The issue is that, when rsync detects that a directory is on another
filesystem, it sends the directory itself but skips the contents. See
send_directory in flist.c: it read
https://bugzilla.samba.org/show_bug.cgi?id=3430
Summary: Error with ACL-patch and -x on mountpoint
Product: rsync
Version: 2.6.6
Platform: Other
OS/Version: FreeBSD
Status: NEW
Severity: minor
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=3304
--- Comment #5 from [EMAIL PROTECTED] 2006-01-19 13:15 MST ---
Surprise: according to the man page of 2.6.6, a receiving-end protect filter is
indeed placed on the partial dir, which is the same as the delay-updates dir.
Never mind comm
https://bugzilla.samba.org/show_bug.cgi?id=3422
--- Comment #7 from [EMAIL PROTECTED] 2006-01-19 12:43 MST ---
(In reply to comment #6)
Great, so I do not need to do the testing. Thanks to all
for the effort.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
https://bugzilla.samba.org/show_bug.cgi?id=3422
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3422
--- Comment #5 from [EMAIL PROTECTED] 2006-01-19 07:46 MST ---
(In reply to comment #4)
OK, I will do that (have done rpm's before), but it will take some time, as I'm
rather busy at the moment (~2 weeks). This way, Wayne also has some
https://bugzilla.samba.org/show_bug.cgi?id=3422
--- Comment #4 from [EMAIL PROTECTED] 2006-01-19 06:57 MST ---
Yes, please do take a recent source RPM or source tarball and try the patch.
If you use rpmbuild, you can get it to apply the patch automatically after
unpacking the source
https://bugzilla.samba.org/show_bug.cgi?id=3422
--- Comment #3 from [EMAIL PROTECTED] 2006-01-19 00:46 MST ---
(In reply to comment #2)
This sounds like a good solution. Thanks, I didn't expect a response so
quickly! Shall I test this out with the latest rsync?
You already did some
https://bugzilla.samba.org/show_bug.cgi?id=3422
--- Comment #2 from [EMAIL PROTECTED] 2006-01-18 20:38 MST ---
Created an attachment (id=1702)
--> (https://bugzilla.samba.org/attachment.cgi?id=1702&action=view)
Makes receiving rsync process deletions only in directories
I found the
https://bugzilla.samba.org/show_bug.cgi?id=3422
--- Comment #1 from [EMAIL PROTECTED] 2006-01-18 19:47 MST ---
I reproduced this bug with my custom rsync 2.6.6.matt.7. According to verbose
output, delete_in_dir("link") seems to be getting called erroneously on the
receiver. I'm tryi
https://bugzilla.samba.org/show_bug.cgi?id=3415
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3422
Summary: dry run fails when encountering dangling symbolic link
Product: rsync
Version: 2.6.4
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=3304
--- Comment #4 from [EMAIL PROTECTED] 2006-01-17 14:56 MST ---
Perhaps the special treatment of the .~tmp~ directory could be implemented by
placing a receiving-end protect filter on any files inside it.
--
Configure bugmail: https://
https://bugzilla.samba.org/show_bug.cgi?id=3304
--- Comment #3 from [EMAIL PROTECTED] 2006-01-17 14:01 MST ---
Perfectly understandable. As for now a hint in the in the manpage (or at
runtime, when 'stale' .~tmp~ directories are encountered) should suffice, since
the current behaviour
https://bugzilla.samba.org/show_bug.cgi?id=3415
--- Comment #2 from [EMAIL PROTECTED] 2006-01-17 13:12 MST ---
here are some more details:
client:
[EMAIL PROTECTED]:/usr/local/sbin/ > rsync --version
rsync version 2.6.6 protocol version 29
Copyright (C) 1996-2005 by Andrew Tridgell
https://bugzilla.samba.org/show_bug.cgi?id=3304
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from [EM
https://bugzilla.samba.org/show_bug.cgi?id=3415
--- Comment #1 from [EMAIL PROTECTED] 2006-01-17 12:20 MST ---
I can't duplicate this. Is the version of rsync that the daemon is running
old? Are the command-lines you cited modified at all from what failed?
--
Configure bugmail: h
https://bugzilla.samba.org/show_bug.cgi?id=3299
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|major |normal
Status|NEW
https://bugzilla.samba.org/show_bug.cgi?id=2790
--- Comment #3 from [EMAIL PROTECTED] 2006-01-16 20:51 MST ---
I've been working on a filename-conversion solution that uses the iconv()
function. After putting a bunch of thought into various designs, I think I
have a good solution tha
https://bugzilla.samba.org/show_bug.cgi?id=3415
Summary: -R and --delete cause --delete to be ignored
Product: rsync
Version: 2.6.6
Platform: Other
OS/Version: Windows 2000
Status: NEW
Severity: major
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=3304
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
--- Comment #1
https://bugzilla.samba.org/show_bug.cgi?id=3392
--- Comment #4 from [EMAIL PROTECTED] 2006-01-15 08:19 MST ---
Nice. It occurs to me that maybe the first call to do_stat should be changed
to link_stat(dest_path, &st, keep_dirlinks) in order to obey --keep-dirlinks
when finding the to
https://bugzilla.samba.org/show_bug.cgi?id=3392
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3392
--- Comment #2 from [EMAIL PROTECTED] 2006-01-10 17:22 MST ---
Created an attachment (id=1661)
--> (https://bugzilla.samba.org/attachment.cgi?id=1661&action=view)
main.c from my custom rsync, showing rewritten get_local_name
--
Confi
https://bugzilla.samba.org/show_bug.cgi?id=3392
--- Comment #1 from [EMAIL PROTECTED] 2006-01-10 17:22 MST ---
This behavior is a consequence of the strange logic in get_local_name in
main.c. If the destination path is given as a file, then rsync uses a "local
name" and accesses the
https://bugzilla.samba.org/show_bug.cgi?id=3392
Summary: fuzzy misbehaving if source is a file
Product: rsync
Version: 2.6.6
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Compone
https://bugzilla.samba.org/show_bug.cgi?id=3382
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3382
--- Comment #1 from [EMAIL PROTECTED] 2006-01-06 14:46 MST ---
Created an attachment (id=1652)
--> (https://bugzilla.samba.org/attachment.cgi?id=1652&action=view)
clearerr() before trying getc() again, otherwise may loop indefinitely
https://bugzilla.samba.org/show_bug.cgi?id=3382
Summary: hang in read() in exclude.test of testsuite
Product: rsync
Version: 2.6.6
Platform: Alpha
OS/Version: OSF/1
Status: NEW
Severity: normal
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=3371
Summary: no way to limit disk IO bandwidth
Product: rsync
Version: 2.6.6
Platform: x86
URL: https://bugzilla.samba.org/show_bug.cgi?id=2800
OS/Version: Linux
Status: NEW
https://bugzilla.samba.org/show_bug.cgi?id=3358
--- Comment #8 from [EMAIL PROTECTED] 2006-01-02 11:42 MST ---
> What is weird about that?
You wrote in a previous comment when I asked why rsync is considering a file
for 30 minutes if it is not checksumming it:
> Because it is trans
https://bugzilla.samba.org/show_bug.cgi?id=3358
--- Comment #7 from [EMAIL PROTECTED] 2006-01-02 11:02 MST ---
(In reply to comment #6)
> This is weird, there is no network activity during this building file list
> phase. However, as soon as it is finished, rsync saturates my network.
https://bugzilla.samba.org/show_bug.cgi?id=3358
--- Comment #6 from [EMAIL PROTECTED] 2006-01-02 10:21 MST ---
This is weird, there is no network activity during this building file list
phase. However, as soon as it is finished, rsync saturates my network.
I thought rsync worked, if
https://bugzilla.samba.org/show_bug.cgi?id=3358
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3363
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
1 - 100 of 148 matches
Mail list logo
