On Mon, Aug 18, 2008 at 11:57:43AM -0400, [EMAIL PROTECTED] wrote:
> which gives me the error "Killed: 9" when it terminates.
That's not an rsync error, but is likely to be a shell message that says
that something else killed rsync. I'd suggest checking the system log
files and/or process history
On Thu 29 Apr 2004, Ryan Holowaychuk wrote:
>
> I am getting the following error
>
> [EMAIL PROTECTED] etc]# rsync 192.168.100.25::backup
You're missing the local target (or source, depending on what you were
trying to do).
> rsync: failed to connect to 192.168.100.25: Connection refused rsync
With file sizes over 2GB I'd suspect problems with >31-bit numbers being
returned from stat() et. al. The rsync version you have on AIX is very
old, and more recent versions handle large files better. The first thing
to do is to upgrade rsync your AIX machine.
- Dave
On Thu, Jan 23, 2003 at 01:
On Thursday, January 23, 2003 12:36:52 PM +0100 Boris Gegenheimer
<[EMAIL PROTECTED]> wrote:
+--
| The versions of the different machines I use are the initiating machine :
| Sun 450
| Solaris 8
| Rsync 2.5.5
|
| The machine that I try to copy from :
| IBM rs6000
| AIX 4.3
| Rsync 2.3.1
|
| Th
r. Version 2.5.6 will have an adaptive block-size.
> -Original Message-
> From: jw schultz [mailto:[EMAIL PROTECTED]]
> Sent: 23. januar 2003 11:34
> To: '[EMAIL PROTECTED]'
> Subject: Re: Error message
>
>
> On Thu, Jan 23, 2003 at 10:55:32AM +01
Message-
From: jw schultz [mailto:[EMAIL PROTECTED]]
Sent: 23. januar 2003 11:34
To: '[EMAIL PROTECTED]'
Subject: Re: Error message
On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote:
> Hello when i get this message what is wrong:
>
> /PTS.
On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote:
> Hello when i get this message what is wrong:
>
> /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large to be
> stored in data type
>
> Regards Boris
Dunno. That error message is not in the rsync source.
Since
Time Connect within Philips, n9hmg on AIM
perl -e 'print pack(,
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
".\n" '
"There are some who call me Tim?"
"David Nickel Jr." <[EMAIL PROTECTED]>
01/1
Almost certainly, something is already using port 873 - probably a
previous invocation of rsync --daemon, or you have inetd listening to it
already.
On a commandline invocation, rsync forks, so invoking it twice in a row
without killing the first one or having the first one die, makes the
seco
On Wed, Jan 09, 2002 at 11:55:24AM -0500, Philip Mak wrote:
> I have a nightly cronjob that uses rsync to back up the files on
> another machine. Sometimes, I see error messages like this:
>
> send_files failed to open
>usr/home/setsuna/Maildir/new/1010573771.27924.lina.aaanime.net: No such file
On Tue, Jun 05, 2001 at 03:28:02PM -0400, eric.deandrea wrote:
> i am running rsync from a shell script out of cron to transfer a module
> between 2 solaris servers. I am getting the error "Argument too long". What
> does that mean? I can run the rsync command without a problem from the
> command
11 matches
Mail list logo