similar to: RFE: extend --keep-dirlinks to files also

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-tuebingen.de

Hi, A minor bug in the manpage was noticed by a Debian user... (Please keep the 418923-forwarded@bugs.debian.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,

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: - Host 1 directory-structure: drwx------ ./1

Hello, I'm trying to push some data from one machine to another via rsync source machine uses rsync 3.0.8, it's a CentOS 5.6 Linux with rsync 3.0.8 package from rpmforge destination machine uses rsync 3.0.6, it's a Scientific Linux 6.0 with rsync 3.0.6 from its repository destination machine is running a rsync daemon with the following configuration: log file = /var/log/rsyncd.log

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 symlinked directories are not being processed for deletions.

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

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

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 source argument with a /. and

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 Aug 20 12:07 bogus -> .. if you use

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

Hello, I a bit surprised to get no replies at all... How come? Lack of information? Lack of clarity? Greetings, Hendrik ------ Originalnachricht ------ Von: "Hendrik Friedel via samba" <samba at lists.samba.org> An: "samba at lists.samba.org" <samba at lists.samba.org> Gesendet: 14.05.2019 20:01:41 Betreff: [Samba] Fw: Btrfs Samba and Quotas >Hello, >

Its possible to get the "file not found" error if the directory is not readable. Are you sure you don't have a permissions problem or something? Reid. On Mon, 2006-08-07 at 13:09 -0400, Hendrik Boom wrote: > On Mon, 07 Aug 2006 09:26:07 -0700, Reid Spencer wrote: > > > Hendrik, > > > > You could also just "touch ~/.cvspass" to create the file

You need to use the script 'llvm-config' to pass correct arguments to g ++: g++ -o broken.o `llvm-config --cxxflags` broken.cpp On Jun 2, 2008, at 9:43 AM, Hendrik Boom wrote: > I took the first two lines of the sample program in the tutorial: > > > hendrik at lovesong:~/dv/lang/hlvm$ cat broken.cpp > #include "llvm/DerivedTypes.h" > #include

On Mon, 07 Aug 2006 09:26:07 -0700, Reid Spencer wrote: > Hendrik, > > You could also just "touch ~/.cvspass" to create the file which should > eliminate the warning. However, since you did a login, and it seemed > successful, chances are the file now exists (containing the blank > password for anon at llvm.org). Indeed, the file is there. > > Reid. >

Just finished the compiling llvm without llvm-gcc from svn. Tried it out. Got g++ -o hlvm.o -c -I/farhome/hendrik/dv/llvm/llvm/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -g -Woverloaded-virtual hlvm.cpp In file included from /farhome/hendrik/dv/llvm/llvm/include/llvm/DerivedTypes.h: 21, from hlvm.cpp:1: /farhome/hendrik/dv/llvm/llvm/include/llvm/Type.h:19:31: error:

Hendrik Boom wrote: > I tried to access the latest LLVM, since several messages here so far have > referred me to it. Now I have no experience with CVS-over-the-net. My > previous experiences with versoin control have been RCS and Monotone. > > Brief summary: > > hendrik at lovesong:~/dv$ mkdir llvm > hendrik at lovesong:~/dv$ cd llvm > hendrik at lovesong:~/dv/llvm$

On Mon, 02 Jun 2008 09:52:16 -0700, Thomas Hudson wrote: > You need to use the script 'llvm-config' to pass correct arguments to g > ++: > > g++ -o broken.o `llvm-config --cxxflags` broken.cpp > > Interesting. When I type the command as you provided it (using cut-and-paste) I get: hendrik at lovesong:~/dv/lang/hlvm$ g++ -o broken.o `llvm-config --cxxflags`

Hendrik, You could also just "touch ~/.cvspass" to create the file which should eliminate the warning. However, since you did a login, and it seemed successful, chances are the file now exists (containing the blank password for anon at llvm.org). Reid. On Mon, 2006-08-07 at 09:14 -0500, John Criswell wrote: > Hendrik Boom wrote: > > I tried to access the latest LLVM, since

Am 08.01.2017 um 17:31 schrieb Jibeji: > Hello, > I am trying to set sieve up on a Centos 7 server. > It's a configuration with postfix, Maildir, MySQL and virtual domains which > works fine. > > I have created a simple .dovecot.sieve in the user's directory: > > # cat /home/mail/domain.com/user/.dovecot.sieve > require "fileinto"; > redirect

I took the first two lines of the sample program in the tutorial: hendrik at lovesong:~/dv/lang/hlvm$ cat broken.cpp #include "llvm/DerivedTypes.h" #include "llvm/Module.h" hendrik at lovesong:~/dv/lang/hlvm$ and tried to compile them using the llvm-dev in Debian testing: hendrik at lovesong:~/dv/lang/hlvm$ g++ -o broken.o -c broken.cpp In file included from