search for: rsynd

https://bugzilla.samba.org/show_bug.cgi?id=14160 Bug ID: 14160 Summary: rsynd in daemon mode should support haproxy proxy protocol Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: core Assignee: wa...

Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch resolves compile problems with the HLINK.C module. The cast on function argument for the qsort() routine was wrong, and not allowing the compile to complete. When the function definiton of the hlink_compare() is corrected to have the const qualifiers, the cast inside the qsort() function call is no longer

Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch resolves compile problems with the checksum.c module. The type (char) was being used where the usage indicated either (void) or (unsigned char) should be used. The const qualifier was added to impove compiler efficiency. There may be more cases in this module where type (char) is being used instead of what appears

Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch is an update to a previous patch that I submitted. The only change from the previous patch is that the const qualifier has been added to write_batch_*() routines to improve compiler efficiency. Because the gdiff -u was done against the distribution it includes the previous patch. The functions with no parameters

Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch resolves compile problems with the IO.C module. The (char) type was being used where (void) was more appropriate based on the actual use of the code. The (char) type was also being used where the usage was actually an (unsigned char). const qualifiers were added to improve compile efficiency. EAGLE> type

...e (at server) with non gziped detination file? PROBLEM: The rsyncd server provides a few *frequently* accessed, slow changing, *big* text files (DNS RBL zones). It seems that the source files are too big to stay in memory caches and rsync sessions cause to many hard disk I/O operations. Making rsynd capable to "ungzip" the files "on the fly" may help to fix the problem by reducing number of I/O operations. -- Andrzej [en:Andrew] Adam Filip anfi@priv.onet.pl anfi@xl.wp.pl Home Page http://anfi.homeunix.net/ [ PageRank 6 ]

Hi I'm using rsync 3.0.3 on a NAS. In the parameter list I use --timeout=1800. However sometimes I get very big timeout times like this one: io timeout after 12220 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(239) [sender=3.0.3pre1] rsynd.conf on the receiving side only defines modules, no timing parameters. How can that happen? What can I do to prevent this? As this is running on a NAS it's not that easy to update rsync. Thanks bye Fabi

...) process new file on backend server 2) upload file to frontend server using scp or rsync over ssh 3) ssh to frontend server to trigger script #3 is only used in a couple special cases I have this tested and working: 1) (same as above) 2) upload file to frontend server using rsync (with patch to rsynd to be verbose in error reporting) 3) (same as above) I would like to be able to trigger a script for #3 instead of having to ssh over (to make the frontend server a bit more autonomous, and simplify the process). I am already maintaining a fork of rsync for #2, so I don't mind making mod...

I'm running FreeBSD 4.6.2 on two different machines. Both machines have rync installed by way of the ports library, but one of them is running it as a server. I followed the directions in the man pages for running the server using inetd. Here is what happens: rsync rsync://myusername@10.0.0.8/ rsync: server sent "rysnc version 2.5.5 protocol version 26" rather than

Hi, everyone~ I want to update rsynd from rsyncd-2.4.4. but I have a matter updating rsyncd-2.5.2 That is make failed. My server is based RedHat-7.0. My configure is successful because i saw message That is 'rsync 2.5.2 configuration successful." This is error messages. I want your advice about This problem. Thank you. ===...

https://bugzilla.samba.org/show_bug.cgi?id=6590 Summary: [sender] could not find xattr #1 for home/jdoe/TheFresh Product: rsync Version: 3.0.5 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: stlman at

An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20091030/c43a29f5/attachment.html>

Greetings - In my logwatch report this morning I noticed reference to an attempt to connect to rsync from an external IP address. It doesn't appear that the connection was successful based on correlating information between /var/log/secure and /var/log/messages. But I am looking for some suggestions for implementing more preventative measures, if necessary. The log information from

Hello, evevryone. thank you for your mails. I used rsync(rsync-2.4.6-2) for backup Server.(My Linux is RedHat7.1) I am very comfortable backup system by rsync. but, I saw this messages in use rsyncd daemon.(/var/log/messages) I don't know mean this messages. but, It is right use rsyncd. and I used rsyncd at every day. but this messages writed log at every minute(?) or every time. What

hi, i hope i'm not reporting something well-known; i tried to understand the available bug tracking information. please excuse me if my problem report should not meet your standards, but i want to direct your attention to the following: http://koffein.org/av/rsync-bugreport/ problem report for rsync 2.6.9 on linux/IA32, 09 Dec 2006 Herwig Wittmann