-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't know what that error means as it is non-specific. However
3.0.4 is very old. Try upgrading your rsync and see if the problem
goes away.
On 08/10/2014 07:08 AM, jerrycww...@hsbc.com.hk wrote:
> Does anyone know what this message is about? I k
On Sun, Sep 01, 2002 at 05:34:31PM -0700, jw schultz wrote:
...
> This sounds like a problem that was fixed a few months ago.
> You might try searching archives. Upgrade to current
> (2.5.5) or the CVS tree.
No, this problem has not been fixed in CVS yet. I posted a hack patch back
in February
quot;
><[EMAIL PROTECTED]>
> > cc: [EMAIL PROTECTED],
>[EMAIL PROTECTED]
> Subject: Re: rsync error: unexplained
>error
les"
<[EMAIL PROTECTED]>
>cc: [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject:
To start with, use the carrage return and don't send html.
This sounds like a problem that was fixed a few months ago.
You might try searching archives. Upgrade to current
(2.5.5) or the CVS tree.
And please send any changes as diff -u against up-to-date
CVS (see diff(1) and patch(1)) encoded
Well there's nothing in that configuration and command that jumps out
at me, except that I don't think the max-delete option is very heavily used
(and therefore not very heavily tested). I suggest putting some debugging
statements int he code to narrow down where that error code of 255 is
coming
Hi,
Sorry I didn't want to fill my original mail up with too much info :-\
Rsync on the Linux box is exactly the same version also compiled from source.
SSH on Solaris Box: SSH Version Sun_SSH_1.0, protocol versions 1.5/2.0.
SSH on Linux Box: OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x
What does your command line look like? Are you running the same
version on the Linux box? It might also help to know the version of SSH
on both ends.
- Dave Dykstra
On Wed, Jul 31, 2002 at 07:03:44PM +0100, Dogsbody wrote:
> Hi All,
>
> I'm new to this group so please be gentle, I have scoure
Check the server's log. By default it goes to syslog, but you can also
make it go to a file with a "log file = " in rsyncd.conf. For security
reasons the rsync daemon mode doesn't give away much information to the
client.
Make sure rsyncd.conf is not group-writable, that's a common problem.
-
I've not seen that one before, but I tried to trace it in the source code.
A -1 from main.c line 842 means that start_client() returned a -1 which
means that start_socket_client returned -1 and there are several things
that can cause that. Mostly they seem to be if the server doesn't do its
part
10 matches
Mail list logo
