similar to: DO NOT REPLY [Bug 5401] New: getpassf() should honor strict modes

I've been running rsync-2.4.2 with an old patch of mine for some time for backup purposes. Due to the recent remote bug, I thought it was time to upgrade, even if the host was behind a firewall. So I dug up the old patch (2.5.2 version attached), that I think I sent ages ago to this list as well. It does the following: (1) Firstly, the only sensible way to run something as

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

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:

Hi Steven, Yes, both file systems are the same. rsync -nri --modify-window=1 <src> <dest> Gives me the following for most files >f..T....... 2015_167_1_1__Boy_What_A_Girl_R2/2015_167_1_1__Boy_What_A_Girl__UHD_DPX_R2/ BWAG_R2_00138428.dpx Although a few have >f..T......n 2015_167_1_1__Boy_What_A_Girl_R2/2015_167_1_1__Boy_What_A_Girl__UHD_DPX_R2/ BWAG_R2_00135909.dpx

https://bugzilla.samba.org/show_bug.cgi?id=5974 Summary: configure --help does not document xattr support properly Product: rsync Version: 3.0.4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

I would like to suggest a feature that I believe would help out one usability aspect of rysnc. The patch I am suggesting will allow the rysnc module to return 1 of multiple secrets from the password file, essentially allowing you to check ANY user's (whom belong to a team) secret to see if it matches. For example: For 2 users (user1 and user2) belonging to team1, it would check

Ville Herva [mailto:vherva@niksula.hut.fi] wrote: > Of course, whether O_TEXT is defined or not does not > necessarily imply the availability of "t", but I > can't think of better alternative. Stratus VOS implements O_TEXT and O_BINARY but does not recognize "t". We have the options defined in ANS C and in POSIX. I'm at home and don't have my reference

Here is part of my backup script: nice -n 15 rsync -avl --exclude=".*" \ --include-from="/home/bob/backup_includes" \ "$fromdir" "$todir" Here is the content of /home/bob/backup_includes /home/bob/.vimrc /home/bob/.gitconfig My problem is that neither the .vimrc nor .gitconfig are copied to the backup directory. I have read the man page about

Hello List, i have got a large File-List which looks like this: ...snip... 165/165950*.jpg 166/166072*.jpg ...snap.... Now i would like to transfer only those file from that list. The rsync command: rsync -avz -F --files-from=/tmp/synclist-small.txt /mnt/ /data/ does not seem to work due to that wildcard. The command: rsync -avz -F --include-from=/tmp/synclist-small.txt /mnt/ /data/ syncs

I seem to be running into a problem where I am trying to rsync from a source directory that lacks write permissions (i.e. r-xr-xr-x). Presumably this is because rsync creates the directory on the destination, then sets the permissions to match the source and then tries to sync the contents of the directory, which it cannot of course lacking write permission in the directory. Is there a way to

the T means that the timestamp is wrong and rsync is not fixing it because you don't have --times or --archive in your command line. On 06/08/2016 08:17 PM, McDowell, Blake wrote: > Hi Steven, > > Yes, both file systems are the same. > > rsync -nri --modify-window=1 <src> <dest> > > Gives me the following for most files >f..T....... >

Hi all, I've recently managed to compile Samba v3.0.24 for OS/2 and have debugged most of the issues. The positive is that relatively few source changes were required to get the daemon working, however, having said that, there are two problems that I'm still having trouble with. 1) smbpasswd is generating a broken password - so password protected clients can't connect. eg.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have been using rsync to backup our primary data stores. It works fine. Here are the options I use for doing that: rsync --recursive --links --times --dirs --stats --delete \ --itemize-changes --quiet --exclude-from=exclude-filename \ /data-store1/ /data-store2/ Recently I have had the need to actually synchronize the files between

I have been using rsnapshot on OS X for a bit now to backup my debian home server to my external HD but have now started getting this error. Shiny:rsync-3.0.6 kurt$ sudo rsnapshot sync /usr/bin/rsync -a --delete --numeric-ids --relative --delete-excluded \ --exclude=mtab --exclude=core --rsh="/usr/bin/ssh -i \ /Users/kurt/.ssh/id_rsa" root at home.thisisnotajoke.com:/home \

Hi to all rsync users. rsync's `--delete' option works fine in the following example: I'm sending all the content of /home/rodolfo from machine1 to /home/rodolfo in machine2: $ rsync --dry-run -vrtul --delete --exclude='/.*' . 192.168.0.2:/home/rodolfo , and --delete works perfectly. Instead, in this other example: $ rsync --dry-run -vrt --delete --modify-window=1 file1

Hi, Some explanations regarding cwRsync: cwRync installers (both client and server) are now available as a paid download bundle. Installer sources, however, are still available as free upon contact. Please keep in mind that installer sources are not enough to build cwRsync installers: You need to build up a complete Cygwin environment, compile/copy binaries in the package. It may be time

Hi! In a project I'm working on, I needed a way to run rsync in daemon mode as a regular user without having the passwords readable to everybody accessing the console. With this chance rsync falls back to Apples keychain access if no secrets file is given. You need to put the passwords into the keychain like this (I do it programmatically bit it can be done manually as well):

$ wc -l /tmp/list 1000 /tmp/list $ rsync -i -aPv --ignore-existing --files-from=/tmp/list /backups/ ut00-s00010:/backups/ building file list ... 3937 files to consider I am totally baffled. That's not such a big deal, but the list I'm *actually* using has twenty *million* files in it. At a couple hundred files a second, if it's going to check 4 times the number of files, that's

The second rsync-2.5.6 pre-release version is now available at: http://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre2.tar.gz ftp://rsync.samba.org/pub/rsync/preview/rsync-2.5.6pre2.tar.gz rsync://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre2.tar.gz There's also a corresponding '.sig' file that contains a gpg signature of the file; the public key is available on the

Hello, I'm author of Lsyncd - the live syncing deamon - http://code.google.com/p/lsyncd/ - a daemon that uses Linux` inotify to watch for filesystem changes - aggregates them for a few seconds and then periodically calls rsync to transfer the changes to target(s). Version 1 was simply aware of directories only, and it called rsync once with --delete -d for every directory in which anything