writefd_unbuffered failed
Hello! A good day to you all. i've installed rsync-2.5.6 on a Red Hat 9.0 box(server) and am using rsync 2.5.6 on a Red Hat 6.2 box(client). In the middle of the rsync transfer, i get the error on the client saying that the server unexpectedly close the connection. Upon checking the logs on the rsync server, i found this entry: Oct 10 14:39:38 linux01 rsyncd[9266]: rsync: writefd_unbuffered failed to write 4096 bytes: phase unknown: Connection reset by peer Any idea what this means? The client is running rsync with the -ar --partial --delete options. Thanks! - Do you Yahoo!? The New Yahoo! Shopping - with improved product search -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: writefd_unbuffered failed
In the middle of the rsync transfer, i get the error on the client saying that the server unexpectedly close the connection. Upon checking the logs on the rsync server, i found this entry: Oct 10 14:39:38 linux01 rsyncd[9266]: rsync: writefd_unbuffered failed to write 4096 bytes: phase unknown: Connection reset by peer Any idea what this means? The client is running rsync with the -ar --partial --delete options. I've gotten similar errors when I had a corrupt filesystem on the server side. Have you fsck'ed both boxes? -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync.h always including syslog.h even when not used.
On Sun, Oct 12, 2003 at 12:38:40AM -0400, John E. Malmberg wrote: jw schultz wrote: On Sat, Oct 11, 2003 at 11:21:19PM -0400, John E. Malmberg wrote: Won't work. LOG_DAEMON is defined in syslog.h. Didn't there use to be a HAVE_SYSLOG or USE_SYSLOG in the source before? Unlikely. That isn't the sort of thing that gets removed. OpenVMS currently does not have a syslog facility, so it does not have a syslog.h. If I put an empty syslog.h in my build directory, than the compiler is happy, so it does not appear to be a needed header file if you do not have such a facility. I can use the empty syslog.h, but I was hoping that this could be a CONFIGURE option, so if and when OpenVMS adds a SYSLOG type facility, it would pick it up with out the local syslog.h file causing a problem. Making it something autoconf detects would be reasonable setting a HAVE_SYSLOG. If you don't have a syslog facility i'd expect you to be getting link errors. I have not seen any that I could attribute to that. The only one I am seeing is for getpass() being missing and I know how to fix that. I'm surprised at that. What about the calls to syslog() and openlog() in log.c? I am trying to restart getting rsync to run on OpenVMS, and find a way around the fork() issue, posibly using POSIX threads. That is tons of work. You might want to look at the work done at Novell. The SYSLOG facility looks like it could map in functionality to the OpenVMS send to operator system service, except that the operator messages go only to the systems in the local cluster. So if needed, I could build an interface to make it work good enough. There does not appear to be any recent CVS snapshots available for download, so I am going with the 2.5.6 release as a base. For a long-term project that may be fairly safe but the resulting code would have to be brought up-to-date with CVS for patches to be accepted. Given the diff between 2.5.6 and CVS head i'd suggest setting yourself use CVS head and keep fairly up-to-date. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
rsync on OpenVMS
On Sun, Oct 12, 2003 at 12:38:40AM -0400, John E. Malmberg wrote: I am trying to restart getting rsync to run on OpenVMS, and find a way around the fork() issue, posibly using POSIX threads. It occurs to me that i may have been overly encouraging in my last followup. Getting rsync to work using threads, whether pthreads or a superior form, will require enormous intrusive changes to the code. While the rsync team has looked favourably on that as a goal the huge changes to the codebase needed to accomplish it make acceptance of patches in that direction unlikely. We don't want crufty half-measures. That the platforms where fork() presents an issue and where pipes have performance limitations appear to either be legacy systems or have an viable guest environment does not much help your cause. I do not know but if OpenVMS support is a problem for rsync proper you might wish to look at pysync or unison which might meet your immediate needs. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
