Il giorno gio, 23/04/2009 alle 17.32 +0200, Paul Slootman ha scritto:
On Thu 23 Apr 2009, Teodor MICU wrote:
Until now I've done this by adding - foo/ on the exclude file. With this
line rsync will not touch any foo/ directory on the receiver.
--delete-excluded will screw this up.
I
Il giorno gio, 23/04/2009 alle 18.01 +0300, Teodor MICU ha scritto:
Until now I've done this by adding - foo/ on the exclude file. With this
line rsync will not touch any foo/ directory on the receiver.
I don't see yet the advantage of using --filter over --exclude but I
hope someone can
On Thu 23 Apr 2009, Ian! D. Allen wrote:
In the man page it says in one place tells the receiving rsync to get
rid of empty directories from the file-list and in another place it says
prune empty directory chains from file-list. The latter sounds like it
operates on the source list, not on
On Fri, Apr 24, 2009 at 10:23:06AM +0200, Paul Slootman wrote:
I don't think the intention is to actually delete empty directories at
the receiving end; only to prevent them being created.
I have not yet found out how to prevent empty directories from being
created when using --max-size or
https://bugzilla.samba.org/show_bug.cgi?id=6280
way...@samba.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from
On Tue, Apr 21, 2009 at 10:39:58AM +0800, Daniel.Li wrote:
I just googled superlifter and found below link, but I can't get any
source code.
Sadly, superlifter never achieved lift-off, so there was never any
source code for it. I created my own test-bed for some new-protocol
experiments (which
On Tue, Apr 21, 2009 at 02:47:41PM +0800, Daniel.Li wrote:
I'm trying to take a look at rsync from code-level.
Is there any software spec or program flow that I can get, which might
give me a basic understanding about the code?
The only thing I can think of is an old how-rsync-works page:
On Thu, Apr 23, 2009 at 02:02:26PM +0200, istrice wrote:
--filter=':r .bar'
This indicates that you want the file .bar to be read at every level of
the destination hierarchy and its contents to be interpreted as filter
commands. That would let you specify localized filtering.
--filter=':r
On Wed, Apr 22, 2009 at 02:20:37AM -0400, Ian! D. Allen wrote:
I want to use --min-size to copy just large files (and their necessary
parent directories), but everything I've tried copies *all* the source
directories, and creates them empty on the destination even if they
don't have any big
On Fri, Apr 17, 2009 at 02:26:25PM +0530, Jignesh Shah wrote:
Hi, Could any one please let me know if there is anyway to overwrite the
log-file if it already exists.
Just change your script that runs rsync to do a rm /tmp/mylogs/myfile
or cp /dev/null /tmp/mylogs/myfile prior to the transfer.
On Fri, 2009-04-24 at 07:36 -0700, Wayne Davison wrote:
On Tue, Apr 21, 2009 at 02:47:41PM +0800, Daniel.Li wrote:
I'm trying to take a look at rsync from code-level.
Is there any software spec or program flow that I can get, which might
give me a basic understanding about the code?
The
On Fri, 2009-04-24 at 07:34 -0700, Wayne Davison wrote:
On Tue, Apr 21, 2009 at 10:39:58AM +0800, Daniel.Li wrote:
I just googled superlifter and found below link, but I can't get any
source code.
Sadly, superlifter never achieved lift-off, so there was never any
source code for it.
On Fri, Apr 24, 2009 at 07:51:35AM -0700, Wayne Davison wrote:
This is because --min-size is a transfer rule, not an exclude rule.
There is no mention of the concept of transfer rule in the rsync
man page. I offer some proposed man page wording changes, below.
The man page says This option
What I want is a client-side log file itemized list of *all* the changes
that rsync did on the remote machine. Using --log-file doesn't
show everything. In particular, --log-file says nothing if the remote
directory was populated using hard links from a --link-dest source.
Any number of remote
14 matches
Mail list logo
