similar to: Crashes maybe due to: "error writing 4 unbuffered bytes"

Dear JW, I spent hours checking and upgrading my hardware. There is nothing wrong with it. It is a 'mature' Pentium-II 400MHz system that has been running my servers WITHOUT ANY CRASHES for nearly 2 years now 24/7 Listen to me: "The crashes are dues to rsync" There is an IDENTICAL report from a totally different source at

I have a filesystem from a different machine nfs mounted on the machine that is running rsync. rsync version 2.5.5 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 64-bit system inums, 64-bit internal inums I am trying to create a backup

I am running a fairly new box, Athlon 1.4Ghz, 512 Mb RAM, RedHat 7.3, rsync rsync version 2.5.4 protocol version 26, it's disk layout is; bash-2.05a# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda6 372M 338M 15M 96% / /dev/sda1 45M 8.9M 34M 21% /boot /dev/sda5 703M 218M 449M 33% /home none 251M 0

I have a filesystem from a different machine nfs mounted on the machine that is running rsync. rsync version 2.5.5 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 64-bit system inums, 64-bit internal inums I am trying to create a backup

I was seeing rsync errors which caused my system installations to fail repeatedly and absolutely. See the error I reported to this mailing list back in June in the Forwarded Message below. When I replaced my NIC cards (realtec chip, 8139too driver) with Linksys cards (and Dec Tulip driver for linux) the problem ceased, rsync worked like it should, and does so repeatedly. My suggestion would be

Hello, I'm running a DOS mode text program under Wine via a Mac OSX Objective-C/Cocoa program. I use NSTask to run Wine and capture stdin, stdout and stderr via NSPipes. I'm having an issue where output from the DOS mode text program doesn't get to the Objective-C/Cocoa program until after the program ends in Wine. I think this is happening because stdout is buffered. Is there a

Hi! I'm experiencing strange performance problems after upgrading to samba 3.2.8 from 3.0.30. For all users except smbadmin (who has administrative rights), read performance is _very_ bad. Looking at the read-requests using filemon and wireshark, I found out that for those users, every read is handled transparently (unbuffered) over the net. (I.e. a 2 byte read-request of the application

Has anyone figured out what is happening with this error? There are many reports of this, but the advise seems to fall short - ie. make sure you are using rsync 2.5.n, make sure the target disk is not full. I have used rsync 2.5.[1,2,4,5] on my rsync server, and I get the same results. The target disk I am working with never gets more than 2% full when the rsync client and server quit talking

How do I do unbuffered output from a rails app? I suspect the question really is "how do I do unbuffered output from ruby" but since it''s for a rails app here I am:-) Also if I understand correctly apache >= 1.3 no longer buffers output?... any thoughts on that also appreciated. Thanks in advance! Tim --~--~---------~--~----~------------~-------~--~----~ You received

rsh gives a reduced environment. if rsync on ApplServ isn't in /bin or /usr/bin, that's probably your problem. It's such a common problem that somebody added the "--rsync-path=" option for just such needs. In my case, i have rsync in /cadappl/encap/bin (symlinked into /cadappl/encap/packages/rsync.something/bin). It's in my path, but not the base system path given

Is it possible to send unbuffered output to client browser from a controller and/or view? If so, how? Thanks!!

On Friday 18 December 2009 17:27, David Greene wrote: > > Here's the updated patch. > > Well, that didn't go through right. Here it is again. Argh! Stupid bug fixed. :) Index: include/llvm/Support/circular_raw_ostream.h =================================================================== --- include/llvm/Support/circular_raw_ostream.h (revision 0) +++

On Dec 18, 2009, at 3:46 PM, David Greene wrote: > > + /// circular_raw_ostream - A raw_ostream that saves its output in a > + /// circular buffer. A better description would be "which *can* save its data to a circular buffer, or can pass it through directly to an underlying stream if specified with a buffer of zero." When it is buffering, what causes it to flush? Your

On Wednesday 16 December 2009 13:35, David Greene wrote: > > Please make BufferSize an 'unsigned' and default it to 8192. Please use > > PRESERVE_STREAM instead of 'false'. Here's an updated version of the circular buffer. Ok to check in? -Dave Index: include/llvm/Support/circular_raw_ostream.h

On Friday 18 December 2009 13:56, David Greene wrote: > On Friday 18 December 2009 13:53, David Greene wrote: > > > > + void releaseStream() { > > > > + // Delete the stream if needed. Otherwise, transfer the buffer > > > > + // settings from this raw_ostream back to the underlying > > > > stream. + if (!TheStream) > > >

On Friday 18 December 2009 19:47, Chris Lattner wrote: > On Dec 18, 2009, at 3:46 PM, David Greene wrote: > > + /// circular_raw_ostream - A raw_ostream that saves its output in a > > + /// circular buffer. > > A better description would be "which *can* save its data to a circular > buffer, or can pass it through directly to an underlying stream if > specified

On Friday 18 December 2009 17:22, David Greene wrote: > On Friday 18 December 2009 13:56, David Greene wrote: > > On Friday 18 December 2009 13:53, David Greene wrote: > > > > > + void releaseStream() { > > > > > + // Delete the stream if needed. Otherwise, transfer the > > > > > buffer + // settings from this raw_ostream back to

On Friday 18 December 2009 12:28, Chris Lattner wrote: > This is looking a lot better, here are some more comments: > > + /// current_pos - Return the current position within the stream, > > + /// not counting the bytes currently in the buffer. > > + virtual uint64_t current_pos() { > > I didn't notice this earlier, but is there any reason for current_pos

On Dec 17, 2009, at 3:41 PM, David Greene wrote: > On Wednesday 16 December 2009 13:35, David Greene wrote: > >>> Please make BufferSize an 'unsigned' and default it to 8192. Please use >>> PRESERVE_STREAM instead of 'false'. > > Here's an updated version of the circular buffer. Ok to check in? This is looking a lot better, here are some more

Hello, While doing a local "rsync" with: rsync -v -auxHS --force / /backup/ (on /backup is mounted another disk), I get these errors: rsync: error writing 4 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(463) rsync: error writing 69 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data