search for: dirlinks

Hi, the combination of --keep-dirlinks and --delete (--delete-during, --delete-delay) erroneously deletes symlinks to directories on the receiver. With --delete-before and --delete-after it works as expected. (rsync version 3.0.3 protocol version, on Debian Lenny) I don't think that this behaviour is intended. Details/example:...

...ebian.org in the Cc list in replies.) diff -u -r1.399 rsync.yo --- rsync.yo 23 Jan 2007 15:34:43 -0000 1.399 +++ rsync.yo 12 Apr 2007 19:30:17 -0000 @@ -724,7 +724,7 @@ also ignored. Using this option in conjunction with bf(--relative) may give unexpected results. -dit(bf(-K, --copy-dirlinks)) This option causes the sending side to treat +dit(bf(-k, --copy-dirlinks)) This option causes the sending side to treat a symlink to a directory as though it were a real directory. This is useful if you don't want symlinks to non-directories to be affected, as they would be using bf(--cop...

Hello folks, trying to make use of the new --keep-dirlinks feature for a synch port; it works excellent but feels incomplete without a way for rsync to ignore recursive links. Example: # ls -la . total 6 drwxrwxr-x 2 bldmstr staff 512 Aug 16 21:42 . drwxrwxr-x 8 bldmstr staff 512 Aug 16 21:41 .. lrwxrwxrwx 1 bldmstr staff 2...

...IVE TCP_NODELAY IPTOS_LOWDELAY IPTOS_THROUGHPUT [data1] path = /data1 comment = data1 read only = false uid = ouruser gid = ourgrp hosts allow = 10.2.1.188 timeout = 300 and from source machine I'm pushing some data like: rsync -av --keep-dirlinks /data/hudson/ 10.2.2.74::data1 it works fine except for the --keep-dirlinks option which doesn't have any effect, so symlinks at the target machine as simply overwritten as if there was no --keep-dirlinks option at all But when I try the same in shell mode, like: rsync -av --keep-dirlinks /da...

If I have a backup script that does the following: (latest 2.6.9 rsync) rsync --archive --hard-links --force --ignore-errors --numeric-ids --keep-dirlinks --delete / /backup I've found that if there is a symlink in place that gets backed up (which goes fine), i.e.: homelink -> /home/ and then that symlink gets changed into an actual directory, i.e.: rm homelink mkdir homelink rsync will actually delete everything in the directory that the...

I've been using the --keep-dirlinks feature of 2.6.3pre1. I also use -x (--one-file-system) and --delete-after. The symlinked directories on the receiver are symlinked to a partition other than the one where the target of the rsync resides (that's the whole point of this nifty --keep-dirlinks feature). I discovered that the s...

It would be nice if rsync offered a way to specify individual dirlinks to keep without keeping all dirlinks. (Unison can do this.) For example, consider the following command: rsync -a --relative src/./ dest/ If rsync refrained from trimming a trailing /. off of source arguments (at least as an option), one could keep a dirlink by passing it as an additional sourc...

https://bugzilla.samba.org/show_bug.cgi?id=5601 Summary: extend --keep-dirlinks to files also Product: rsync Version: 3.0.2 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: hendrik.maryns@uni-tue...

Hi, I have gone through the rsync documentation and also tested same both --no-implied-dir and --keep-dirlinks options. My question is what is the difference between these options in below scenario? I have /foo/bar is the symlink to /foo/baz at source and same directory structure with symlink is there at destination. When I sync the data from /foo/bar/* with --relative option specified, I am ending with l...

https://bugzilla.samba.org/show_bug.cgi?id=4037 Summary: Rsync should obey --keep-dirlinks when searching basis dirs Product: rsync Version: 2.6.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedB...

Hi, I just read the thread http://lists.samba.org/archive/rsync/2004-June/009678.html which describes how --keep-dirlinks came to be. My use case is similar, but I?d like a similar option for files as well. Setup: in my public_html I have some symlinks which I send over as files, with -L (for various reasons: partly, because they are copies of current work which is done elsewhere, or because several websites use...

I''m running 2.6.6 on a red hat EL3 system. using the following command, rsync -rlptDvzL --stats --include=a/ --include=a/dir/ --include=a/dir/symlink/ --include=a/dir/symlink/dir2/ --include=a/dir/symlink/dir2/dir3/ --exclude=''**'' /export/stuff remote::stuff I expect the "symlink" (which is really a symbolic link to a directory) to be preserved on the

Wayne, Attached is a patch worth of suggested man page improvements for --no-implied-dirs and --keep-dirlinks. I think new users would find my explanations clearer and more complete, although you may want to make additional changes. I regenerated rsync.1 and the patch includes changes to it, but my yodl is somewhat weird, so I suggest you run yodl again yourself. -- Matt McCutchen hashproduct@verizon.ne...

...about these directories. Therfore I use -R (--relative) and -H. so far ok but: I create symlinks to the source-directories via script because src-dirs have changing names (date and time of backup) and I want to have constant directory names on target. How can I achieve that? I thought -k (--copy-dirlinks) would work but this replaces ALL symlinks to dirs which exist in the copied tree to real directories. I just want to have the "symlink dir conversion" done on the starting directories dir1 and dir2 cd /tmp/backup rsync -RaH --copy-dirlinks --stats --delete --progress dir1 dir2 dest...

Well, I just did a dirty test: * mklink link.txt "textfile.txt" * mklink /D DIrLink "Directory" * copied it to a samba share via Explorer (drag and drop). * copied it to a Windows share via Explorer (drag and drop). In both cases, it copied the contents of "textfile.txt" as "link.txt", definitely not a symlink (windows or otherwise). Same with

I'm trying to figure out if there is some way to run an rsync daemon which makes a mix of "real" and symlinked folders available to a client such that all the folders appear as "real" to the client. I realize the --copy-links and --copy-dirlinks accomplish this when invoked from the client side (and that is currently how I am accomplishing this). Is there any way to essentially "force" those options from the daemon end? So that to a client, a symlinked dir will always appear as the referent dir. If not, then if at all possib...

Hi, this is possibly a bug report (I'm not sure if this is a feature). It's related to the --keep-dirlinks option, when combined with --delete . I have the following directory structure on server A: ls -lR software software: total 238 drwxr-xr-x 2 biolord bioinf 1024 Sep 20 10:49 EMBOSS/ lrwxrwxrwx 1 biolord bioinf 6 Feb 5 2003 MSE -> EMBOSS/ lrwxrwxrwx 1 biolord bioinf...

I haven't done much with Folder Redirection yet (gosh, I really need to), but are Junctions and Symlinks _generally_ redirected/transferred cleanly?

Hi On the rsync Server we have rsync path set to say, path= /x/y where 'y' is symlink to some other directory say 'z' on the same machine. Now is there a way to sync 'y' on remote client preserving the symlink as it is and also copy the actual contents from 'z' to say 'z' on the client machine. I have tried using '-l ' option which copies

...operly (older + - Using --only-write-batch to a daemon receiver now works properly (older versions would update some files while writing the batch). - Avoid outputting a "file has vanished" message when the file is a broken - symlink and --copy-unsafe-links or --copy-dirlinks are used (the code + symlink and --copy-unsafe-links or --copy-dirlinks is used (the code already handled this for --copy-links). - Fixed the combination of --only-write-batch and --dry-run. @@ -160,7 +160,7 @@ Changes since 2.6.9: ACL-patched versions of rsync, apply the...