similar to: [PATCH] s3: Add "spoolss backchannel" parameter

Hi! I am doing backups from a number of machines to an rsync server. For some time I was trying to come up with a solution, which would prevent users from peeking at each other's files, which are backed up. Finally, I've hacked rsync, introducing a new option "write only" for rsyncd.conf. When set to true, this option forbids the transfers from server to the client, thus solving

Hey all, Like a lot of folks, I use rsync to pull content out to production web servers. Tastes great, less filling. Here's what I'd like to be able to do: Sometimes a web tree is not ready to sync, for whatever reason. I have many modules available, so stopping ryncd is not an option. I'd like to be able to tell rsync in daemon mode "this particular module is not available at

T.D.Lee@durham.ac.uk wrote: > > > But we'd like to go one step further and have the return code from preexec > be used to continue or abort the connection being established. The script > above would be modified to generate this return code. > > Looking through the source code (smbd/service.c), it doesn't seem to check > the return code (calling smbrun to do the

----- Forwarded message from Jeremy Allison <jra@samba.org> ----- From: Jeremy Allison <jra@samba.org> To: samba-technical@samba.org Cc: jra@samba.org Subject: Patch to improve Samba write speeds on Linux ext3 with 3.2.x Reply-To: Jeremy Allison <jra@samba.org> Hi all, Intel recently did some research on Samba write speeds, tested in Linux using ext3 resulting in the following

We use rsync to provide an rsync share on a linux server with a javascript program on Windows clients which ensures all client data is backed up each morning. After making no progress with my posting last month regarding making a module upload only to prevent someone from manually downloading the rsync share obtaining other users work (exclude = * wasn't possible because we need --delete to

In the bufferbloat age, anything that can make for a kinder, gentler bulk transfer protocol seems desirable. This add support for user and server selectable congestion control algorithms. As examples: --congestion-alg=lp # For the tcp-lp algorithm on the command line Or in a subsection: [mystuff] congestion alg = westwood # for a wireless connection And diffserv support: --diffserv=8 for

Hi folks, This is a patch for rsync 2.6.9 - I'm not sure if this is the proper vehicle for submitting them. It's been working great for us for months, and I hope it's seen as offering useful utility in general. Steve (who is not a subscriber to this list) --- Stephen J Friedl | Security Consultant | UNIX Wizard | +1 714 544-6561 www.unixwiz.net | Tustin, Calif. USA |

Ok, this one actually produces the message I intended... Questions for the community and team: 1) should warnings be at DEBUG(2, and notices at 3? 2) should errors like "path points to non-dir" cause a fatal error as well as an error message? 3) should the share names be in []s in the messages? --dave -------------- next part -------------- 1770c1770,1772 < incomplete or

I've been unhappy for some time with the weak checking of service self-consistency in .../source/param/loadparm.c's "service_ok" function. Here's my initial draft of a better one, in diff format. Suggestions and criticism welcome! --dave -- David Collier-Brown, | Always do right. This will gratify 185 Ellerslie Ave., | some people and astonish the rest. Willowdale,