Please ignore this thread for the moment.
At present, there are no complete copies of the file in question at the
destination.
I was sure yesterday, but OTOH I can't imagine why existing copies would
have been deleted. It's not supposed to work that way.
I've been monitoring the situation in sc
Wayne Davison wrote:
On Wed, Sep 29, 2004 at 01:36:14PM +0800, John wrote:
Is there something in the above options I should add or remove?
I don't see anything wrong that should prevent the hard-linking from
happening. If you do an "ls -li" on the source files, do they all show
the same in
It is my understanding after reading all manuals and postings that
--delete only works, when rsync is doing recursive dir-to-dir
synchronization. Like in the following example
local host:
/dir/dira
/dir/dirb
/dir/dirb/file2
remote host:
/dir/dira
/dir/dira/file1
/dir/dirb
/dir/dirb/file2
If we d
https://bugzilla.samba.org/show_bug.cgi?id=1804
--- Additional Comments From [EMAIL PROTECTED] 2004-09-29 13:57 ---
fyi: the bug also shows up on openbsd (3.5)
(see http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=3926 )
and IMHO also posibil present present on mac OS
On Wed, Sep 29, 2004 at 01:36:14PM +0800, John wrote:
> Is there something in the above options I should add or remove?
I don't see anything wrong that should prevent the hard-linking from
happening. If you do an "ls -li" on the source files, do they all show
the same inode number? I'll run some
On Wed, Sep 29, 2004 at 11:28:04AM -0700, jim wrote:
> One more question. Does rsync intentionally behave differently if
> it's talking over ssh vs directly over a socket?
The main difference is in the protocol startup (since we have to send
some things over the socket in daemon mode that get se
OK, I'll try it.
One more question. Does rsync intentionally behave differently if it's talking
over ssh vs directly over a socket?
---Original Message---
> From: Wayne Davison <[EMAIL PROTECTED]>
> Subject: Re: rsync 2.6.2 hang (was rsync 2.6.2 crash)
> Sent: 29 Sep 2004
On Wed, Sep 29, 2004 at 10:08:16AM -0700, jim wrote:
> Do you have a gut feeling as to where I should look first, or what the
> issue might be? Do you suspect rsync or ssh as the likely culprit?
It's hard to know, but I'd suggest starting by assuming it's rsync's
fault and going from there. The
On Wed, Sep 29, 2004 at 12:04:21PM -0400, Tony VanScoy wrote:
> $ rsync --version
> rsync version 2.6.0 protocol version 27
Allow me to answer by reference to things I've said in the past:
http://lists.samba.org/archive/rsync/2004-January/008406.html
http://www.mail-archive.com/[EMAIL PROTECTED
Do you have a gut feeling as to where I should look first, or what the
issue might be? Do you suspect rsync or ssh as the likely culprit?
>Yes, others have experienced hangs when using rsync over ssh under
>cygwin. If possible, stick with the rsync daemon protocol for cygwin
>transfers and it sh
On Wed, Sep 29, 2004 at 08:44:43AM +, David Evers wrote:
> I'm not seeing how we know that ssh has finished messing with stderr
> by the time the patch comes to try to set it back to blocking.
The reason there's no race is that this call comes after we've begun to
talk over the socket to the r
i want to backup a website every day, but only get the changed files.
Otherwise just hard link to yesterdays file. So I'm trying
--link-dest. here is the script (backup.sh) I'm trying to use
#!/bin/bash
if [ -z "$1" ]; then
echo usage: $0 rsync_module
exit
fi
BACKUP_DIR=/ho
The attached patch fixes the problem by putting our stderr fd back
into blocking I/O mode.
A bit of digging in the openssh bugzilla throws up this:
http://bugzilla.mindrot.org/show_bug.cgi?id=26
which suggests that ssh really does want to keep stderr
non-blocking :-(
Cheers,
David
--
To unsub
The attached patch fixes the problem by putting our stderr fd back
into blocking I/O mode. I don't see why ssh should be playing with
our stderr fd in the first place (since we're the one calling ssh,
not the one being run by ssh). Does anyone see a problem with this
change?
With this patch, isn'
On Tue, Sep 28, 2004 at 03:19:43PM -0700, jim wrote:
> I am still having problems when I throw ssh into the mix. At least
> now, things don't crash, but they do hang.
Yes, others have experienced hangs when using rsync over ssh under
cygwin. If possible, stick with the rsync daemon protocol for c
15 matches
Mail list logo
