On Tue, 27 Jul 2004, Steve Bonds <[EMAIL PROTECTED]> wrote:
>
> bigfile
> rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown":
> Broken pipe (32)
> rsync error: error in rsync protocol data stream (code 12) at io.c(902)
> The receiver backtrace is:
>
> -
> (gdb) bt
> #0
> if you're using rsync on Windows, you already are using cygwin
> (knowingly or not, rsync is available on Windows ONLY through CygWin, as
> far as I know)
I got my copy direct from cwrsync.
http://www.itefix.no/cwrsync/
It seems to use a Cygwin dll though.
--
To unsubscribe or change option
On Wed, Jul 28, 2004 at 02:06:45AM -0500, John Van Essen wrote:
> Wayne - why is the "write failed" message not being displayed?
A local-to-local transfer treats the sending side as the client, so
that's the only side that lets output messages. My guess is that the
error message from the receiver
Hello,
I'm having trouble transferring files from an rsync server on Mac OSX to a
Linux machine. I'm doing everything as root on both ends to make sure it's
not a permissions issue, but still can't get all the files to transfer.
I have the rsync server running on OSX as root, like this:
server:
In an attempt to copy a particular directory or file from the "primary"
server to the "backup" server - it looks as though rsync is wanting to work,
but nothing is copied.
primary - 10.28.123.232
backup - 10.28.123.230
rsyncd.conf file (on primary server)
---
uid = 0
gid = 0
use
On Wed, Jul 28, 2004 at 02:44:34PM -0400, Anthony DiSante wrote:
> I'm doing everything as root on both ends to make sure it's
> not a permissions issue, but still can't get all the files to transfer.
First off, look for error messages in the log file that the daemon is
logging into (it will be o
On Wed, Jul 28, 2004 at 03:27:56PM -0600, Scott Miller wrote:
> [EMAIL PROTECTED] root]# rsync -rv 10.28.123.232::web
[...]
> Now, I put a file in the /var/www/html directory of the Primary server - but
> it never seems to get transfered to the backup server.
That command is a list command, not a
Attached is some public domain source code that tests mkstemp() to see if
it functions properly by creating a 2GB sparse file in /tmp, first via the
normal open()/lseek()/write() pathway, then using
mkstemp()/lseek()/write().
Perhaps this could be migrated into an rsync test case? My only concern
