similar to: [Bug 1673] New: Verbose dry run doesn't report replacements of symlink with directory

Displaying 20 results from an estimated 3000 matches similar to: "[Bug 1673] New: Verbose dry run doesn't report replacements of symlink with directory"

2004 Sep 17
0
[Bug 1673] Verbose dry run doesn't report replacements of symlink with directory
https://bugzilla.samba.org/show_bug.cgi?id=1673 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |minor Status|NEW |ASSIGNED Priority|P3 |P4 ------- Additional
2005 Feb 12
0
[Bug 1673] Verbose dry run doesn't report replacements of symlink with directory
https://bugzilla.samba.org/show_bug.cgi?id=1673 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From wayned@samba.org 2005-02-12 14:37
2004 Sep 08
2
--keep-dirlinks in combination with --one-file-system
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.
2003 Dec 17
1
TODO hardlink reporting problem - fixed?
On Mon, 15 Dec 2003, jw schultz <jw@pegasys.ws> wrote: > OK, first pass on TODO complete. .... This hardlink bug report is nearly 21 months old... So I took a look at it using 2.5.7. See below. > BUGS --------------------------------------------------------------- > > Fix hardlink reporting 2002/03/25 > (was: There seems
2002 Dec 09
0
Mailman 'held' messages (was SPAM on List...)
On Mon, 9 Dec 2002, Martin Pool <mbp@samba.org> wrote: > >Mailman holds some suspicious messages for filtering by the admin. >However, for samba.org, this means about 80 messages per week, which >have to be handled through a clunky web interface, and which take time >away from more useful tasks. This is not acceptable. Pah! :) Try 100+ messages per day, with 200+ at the
2002 Nov 07
0
Bogus rsync "Success" message when out of disk space
To the rsync maintainers: When rsync 2.5.5 is pulling files and the target disk runs out of space, this is what the tail end of the message stream looks like (w/--verbose): write failed on games/ghostmaster/ectsdemo2002.zip : Success rsync error: error in file IO (code 11) at receiver.c(243) rsync: connection unexpectedly closed (152112 bytes read so far) rsync error: error in rsync protocol
2013 Dec 02
2
symlink in -R src_dirlist and real dirs on target
Hi folks, I have a bunch of directories to mirror via rsync. I have lots of hardlinked files spread 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
2009 Oct 03
1
--keep-dirlinks --delete erroneously deletes symlinks to directories
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
2004 Aug 20
3
Using --keep-dirlinks : recursive symlinks problem
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
2004 Sep 21
0
Rsync 2.6.3pre2 released
I have released rsync 2.6.3pre2 -- the second (and final) pre-release version of 2.6.3. Please help out with the testing so that the code gets a good workout before 2.6.3 is released. (Note that this version will not be in testing for as long as 2.6.3pre1 was -- I'd like to get it released in a week or two, if possible.) To see what has changed since 2.6.2, read this text file:
2004 Sep 21
0
Rsync 2.6.3pre2 released
I have released rsync 2.6.3pre2 -- the second (and final) pre-release version of 2.6.3. Please help out with the testing so that the code gets a good workout before 2.6.3 is released. (Note that this version will not be in testing for as long as 2.6.3pre1 was -- I'd like to get it released in a week or two, if possible.) To see what has changed since 2.6.2, read this text file:
2004 Sep 20
1
rsync version 2.6.3pre1 protocol version 28
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
2007 Oct 29
2
symlinks that become directories question
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
2011 Jun 28
2
rsync 3.0.6 and keep-dirlinks in daemon mode
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
2008 Jul 09
0
DO NOT REPLY [Bug 5601] New: 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
2007 Apr 12
2
error on --copy-dirlinks shortform in manpage
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,
2006 Aug 20
2
DO NOT REPLY [Bug 4037] New: Rsync should obey --keep-dirlinks when searching basis dirs
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
2007 Nov 04
1
Keeping individual dirlinks
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
2009 Jun 29
1
difference between --no-implied-dir abd --keep-dirlinks ?
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
2012 Dec 18
1
Prevent dereferenced path of symlinked directories from printing on client side log output
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