I believe I have encountered a nasty bug with rsync 2.6.6
"--delete-excluded" option. When this is enabled, rsync's operation
appears to break entirely.
I have a script that I've been using for a few years. The script
hasn't changed in the last year or so. Recently I upgraded from
SuSE 9.3 t
* Wayne Davison ([EMAIL PROTECTED]) [20051209 12:10]:
> On Wed, Dec 07, 2005 at 10:45:35PM -0800, Raymond Keller wrote:
> > In my source I have a directory that changed to a file. I know this
> > requires --force or --delete, but using --only-write-batch I get no
> > err
https://bugzilla.samba.org/show_bug.cgi?id=3277
--- Comment #3 from [EMAIL PROTECTED] 2005-12-09 16:19 MST ---
Instead of treating -o and -g specially, I think it is time rsync had separate
archive options for "running as a normal user for a normal copy", i.e. using
default destinatio
On Wed, Dec 07, 2005 at 10:45:35PM -0800, Raymond Keller wrote:
> In my source I have a directory that changed to a file. I know this
> requires --force or --delete, but using --only-write-batch I get no
> error until I attempt to apply the batch.
That's correct -- there's no problem generating t
Wayne Davison wrote:
> On Thu, Nov 24, 2005 at 03:22:23AM +, Jamie Lokier wrote:
> > Is there any likelihood of changing the rsync code to use threads
> > instead of processes?
>
> I just thought about this a bit more, and it didn't seem as large a task
> as I had originally assumed it would b
Nelson H. F. Beebe wrote:
> List traffic today asks about changing rsync to use lightweight
> threads instead of heavyweight fork.
>
> Before rushing into building a threads version of rsync, please READ
> this recent article
You didn't post a link directly to the article, just to the gateway pag
thanks for your reply.I have tried that also but still getting the same error
On 09/12/05, Paul Slootman <[EMAIL PROTECTED]> wrote:
On Fri 09 Dec 2005, gg gg234 wrote:>> ssh: connect to host x.x.x.x port 22: No route to host
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
On Fri 09 Dec 2005, gg gg234 wrote:
>
> ssh: connect to host x.x.x.x port 22: No route to host
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(420)
>
> this is related to ssh i believe.But when i try t
Hi,
When i try to run rsync command from command linne it is working fine.Below is the command
/usr/bin/rsync --compress \ --verbose \ --rsh=ssh \ --times \ --owner \ --group \ --ignore-times \ --
