similar to: rsync kioslave - future direction

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm (very slowly) working on a kioslave for rsync. At this stage I'm just exec()ing the rsync binary. If you want to know how far I have to go, see: http://www.cuneata.net/rsync-kio.html for the bad news. One question that I'm still grappling with is how to handle motd. I have a very rough heurestic for finding it (everything up to the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 G'day The attached patch adds "first draft" support for service location protocol, using OpenSLP (http://www.openslp.org). This allows you to automagically discover all the rsync servers on your network (which is defined in terms of your SLP configuration - typically equal to multicast scope, but you can change it around with

I am getting the following error when trying to connect to http://localhost:901 500 Server Error chdir failed - the server is not configured correctly Are there any known fixes for this ? Also: I noticed that some of the directives, such as datadir, might be non-functional or ignored elsewhere in coding of swat Could this be the cause of the above errors ? Finally here is the cli output

Dear List, I just googled "superlifter" and found below link, but I can't get any source code. http://superlifter.sourceforge.net/ Any help or info on this is mostly appreciated. And sorry for the trouble, if it's NOT allowed to post here. THanks. -- Daniel

I would like to suggest that different programs be used for backups than for file distribution. While the two applications have a lot in common, and could probably share a common library, there are some significant differences in what they need to do. These differences can add needless complexity to the design if a single program is used to do both. A backup program is mainly concerned with

I'm interested in these very questions (librsync-rsync relationship, remaining limitations of rsync, active prospects for ground-up rewrites), Google searches for rsync info have proved a little too vague due to the programs ubiquity. Much has certainly changed since this was written, could some people with knowledge in these areas could update martin's response for the state of rsync,

CentOS Errata and Bugfix Advisory 2014:1045 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1045.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 8bccc9a244ce4eba1cbdfc5fa9256861f6de5dcce600915c101dfcd0c926edc1 kdesdk-4.10.5-6.el7.x86_64.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

> From: jw schultz <jw@pegasys.ws.invalid> > > On Fri, Jul 26, 2002 at 09:03:32AM -0400, Bennett Todd wrote: > >>2002-07-26-03:37:51 jw schultz: >> >>>All that matters is that we can represent the timestamps in >>>a way that allows consistent comparison, restoration and >>>transfer. >> >>A very good statement indeed. There are

Hello, I using red-had Linux 8.0 with two IP addresses. On the first IP rsync is listen to port 873 and Apache web server to port 80. What I need to do so that rsync will listen also to port 80 on the second IP address ? Thanks, Addady

Hey everyone, I am a final semester MCA student. I've chosen rsync as the subject of my project for my graduation. Hence I would appreciate it if someone could guide me with some ideas on how I can contribute to rsync. I will work hard to implement whatever suggestions that you can all give me. I would definitely like to know what are some of the issues concerning rsync. May be I can then

Hello, Hello all, I've been working on a construction to make access to networkresources easier, using autofs. The construction permits user access to networkresources like a Samba/Windows server with cifs, FTP servers using curlftpfs and SSH using sshfs (fuse), in one directory created with autofs. I'm sure more services like nfs and ipx are possible, but I did not test that. (in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== "Patience is the companion of wisdom." Saint Augustine ============================================================== Release Announcements ===================== This is the first stable release of Samba 3.2.0. Please be aware that Samba is now distributed under

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== "Patience is the companion of wisdom." Saint Augustine ============================================================== Release Announcements ===================== This is the first stable release of Samba 3.2.0. Please be aware that Samba is now distributed under

> Qualities > > 1. Be reasonably portable: at least in principle, it should be > possible to port to Windows, OS X, and various Unixes without major > changes. In general, I would like to see OpenVMS in that list. > Principles > > 1. Clean design rather than micro-optimization. A clean design allows optimization to be done by the compiler, and tight optimization

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm playing with valgrind, and ran it with rsync. I'm really not sure if I'm understanding either the tool or the code, but here is an example. When we're downloading a file in client-server mode, we end up in main.c::client_run(), doing a call to flist.c::recv_file_list(). Around line 1036, we do a malloc of the file list:

I am rsyncing several hunderds of thousands of files in several directories. The way I got rsync to work for me was I wrote a script which NFS mounts the directory I am rsyncing first before starting, and then it goes through the directories and rsyncs them in bite sizeable chunks by going a few directories deep and starting there.. Is there any way to have this as an option inside rsync

Hello, I'm currently evaluating the possibility of implementing a rsync client in a project for my company. The platform used is currently not supported and implementing the client from scratch currently seems to be the most feasible approach. For that I'd be very much interested in a description of the protocol that rsync talks on port 873. Is such a description available somewhere? I

Hi there, I haven't yet delved into the rsync source code, and thus would need to ask a few questions first before going into the wrong direction. We have not, one but several cases[1] of doing Disaster Recovery type backup/synchronization with typically 1 to 2 million of files. Now yes, I know I can go and write a perl/python/<flavour_of_the_year> script to recursively do the

For the small number of people who are checking this out, I released version 0.05 a couple days ago (and only mentioned it on my new-protocol web page) followed today by 0.06. Some highlights of the two releases: - We handle symlinks now in our recursive synchronization mode. - Directory scanning is no longer limited to one active directory at a time (which was sorely needed when all the