similar to: rsyncd + scripting

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

Hi, I'm trying to get rsync 2.5.6 to authenticate users via openldap-2.0.23. I was looking through the mailing list archives and found a patch for rsync-2.4.6 that does this for me. I was just wondering if this is still valid, or if there has been a new patch or new implementation that has superceded this patch. Any help would be great. The message I am referring to is as follows:

Attached please find unified diffs against Samba 2.0.6. I'm hoping that others will find it useful and that it may even find its way into Samba 2.0.7 This patch does two things: - Modifies the handling of the 'netbios name' parameter so that standard_sub_basic() is run on its value when the 'netbios name' parameter is processed. This has to be done this way because

--- .../smbdotconf/printing/spoolssbackchannel.xml | 16 ++++++++++++++++ source3/include/proto.h | 1 + source3/param/loadparm.c | 12 ++++++++++++ source3/rpc_server/srv_spoolss_nt.c | 6 ++++++ 4 files changed, 35 insertions(+), 0 deletions(-) create mode 100644

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

I'm preparing to roll out a bunch of win XP clients and and am running down all the quirks that come up in the application log on my test box. 1) AutoEnrollement fails - samba is not an active directory so this makes sense it must be disabled by editing the group policy with gpedit.msc computer configuration->windows settings -> security settings -> public key policies ->

Hi, a few months ago I posted a message about using LDAP to store rsync secrets in LDAP. I received a response about patching the rsync source code with a patch file. I am now finally getting around to doing this, and when I tried to use the patch command 'patch --verbose ./rsync-2.5.6/authenticate.c rsync-ldap.patch' , it gives me the following error: Hmm... Looks like a unified diff

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

In case others find this of value, I wrote a patch to rsync 2.5.6 to give rsync in --daemon mode the ability to run a pre-transfer and post-transfer command. These options handle our need to prepare a server to receive files and to do some processing after receiving files. The options for /etc/rsyncd.conf are pretransfer script = /some/command/to/run posttransfer script =

Dear List, Currently, I read this in clientserver.c, line 148. motd = lp_motd_file(); I have googled, but didn't the definition of char *lp_motd_file(void). Can anyone help to explain the following code segment. Many thanks. #line 147 ~ 160, in clientserver.c, version 3.0.5 > if (!am_client) { > motd = lp_motd_file(); > if (motd && *motd) { > FILE *f =

This is a patch to control unix permissions when uploading to a rsyncd-server by setting rsyncd.conf options. cu, Stefan -- Stefan Nehlsen | ParlaNet Administration | sn@parlanet.de | +49 431 988-1260 -------------- next part -------------- diff -ur rsync-2.5.5/loadparm.c rsync-2.5.5-umask/loadparm.c --- rsync-2.5.5/loadparm.c Mon Mar 25 05:04:23 2002 +++ rsync-2.5.5-umask/loadparm.c Sun Mar 2

Hi, If anyone is interested, the included patch to rsync-2.6.2 allows you to specify the port number for an rsync server as a global option in rsyncd.conf with 'port = <N>' (where <N> is your favorite port number). Note that this parameter only takes effect when the server is started, not when clients connect. Also, specifying the port in rsyncd.conf takes precedence

While I was working on the avoid-reverse-lookup patches, I found a flaw in the daemon's behavior of reloading the configuration on each connection. If I remove a module parameter (in my case, "hosts allow") from the global section, the removal does not take effect. This is because loadparm.c does not reset sDefaults to the application defaults before reloading the configuration.

As you all know, rsync doesn't have any special handling for Mac OS X HFS+ resource forks. Kevin Boyd made RsyncX and rsync_hfs, to address this gap, but they only work when the destination filesystem is also HFS+. I haven't been able to find any references to an rsync that is capable of syncing from HFS+ to UFS (etc). The only solutions I've seen involve lots of preprocessing

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 |

hi*& Samba has troubles with joining to NT PDC, that has some scope id because: 1. smbpasswd does not know anything about scope id and you haven't any chance to join into NT PDC. 2. also many utils like smbmount doesn't know scope id 3. In smbclient you can specify scope id, but you should remember it and etc. It's not so usable. I'm asked about these problems in samba

I use rsync to mirror several servers. I run RH7.3 My rsyncd.conf file is: motd file = /etc/rsync.d/rsync.motd log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid lock file = /var/run/rsync.lock hosts allow = 10.1.2.200 10.1.2.201 hosts deny = 0.0.0.0/0.0.0.0 use chroot = yes max connections = 3 #syslog facility = [website] path = /var/www/website comment = Connex Live WWW

Hi, I spent a little bit of time trying to debug a segfault in rsync 2.5.0, and after discovering it was in loadparm.c, I noticed that the bug had been worked around in the current CVS by removing a free() statement. That fix seems less than optimal; here's a patch which should fix the memory leak. -------------- next part -------------- --- loadparm.c.~1.40.~ Sun Dec 2 03:16:15 2001 +++

Hi all, in our LAN we use a Samba server (version 2.2.9) on Linux (Debian Woody) to provide file services to workstations running (mostly) W2K. WinCVS is a GUI frontend to the popular CVS version control system. After the swap to and from daylight savings time WinCVS erroneously flags all files in cvs working directories on Samba shares as modified (because of the icon color WinCVS users refer to