samba-bugs@samba.org
2008-Jan-22 13:45 UTC
DO NOT REPLY [Bug 5223] New: Options to limit --one-file-system at the source or destination.
https://bugzilla.samba.org/show_bug.cgi?id=5223
Summary: Options to limit --one-file-system at the source or
destination.
Product: rsync
Version: 3.0.0
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy: hans@deragon.biz
QAContact: rsync-qa@samba.org
Currently, the --one-file-system applies to both the source and destination and
this is a problem.
In my source, I have a symlink pointing to a directory on another device which
I would like to have copied. I thus use --copy-unsafe-links.
I also use --delete. This is dangerous because if there is a bug in my script,
I would not like the destination to become suddenly / and deletion occurs on
mounted network drives (granted, the machine would be toast, but the damage
would be limited to the machine; not the corporate network).
If I make use of --one-file-system, the symlink at the source gets ignored. So
I need a --one-file-system option that applies only to the destination,
probably named something like --one-file-system-at-destination.
Could that be easily implemented? The following two options would be nice:
--one-file-system-at-source
# Limit to one file system at the source.
--one-file-system-at-destination
# Limit to one file system at the destination.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
samba-bugs@samba.org
2008-Feb-07 03:40 UTC
DO NOT REPLY [Bug 5223] Options to limit --one-file-system at the source or destination.
https://bugzilla.samba.org/show_bug.cgi?id=5223 ------- Comment #1 from matt@mattmccutchen.net 2008-02-06 21:41 CST ------- Another approach would be to add --server-opt=OPT and --suppress-server-opt=OPT options to let the user tweak the list of options sent to the server. Then, for a push, --one-file-system-at-source would become -x --suppress-server-opt=-x and --one-file-system-at-destination would become --server-opt=-x . A pull would be the other way around. --server-opt would also be useful for things like --fake-super and --log-file that currently have to be stuffed in the --rsync-path . -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
samba-bugs@samba.org
2008-Mar-15 08:10 UTC
DO NOT REPLY [Bug 5223] Options to limit --one-file-system at the source or destination.
https://bugzilla.samba.org/show_bug.cgi?id=5223
wayned@samba.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- Comment #2 from wayned@samba.org 2008-03-15 03:10 CST -------
There is a diff in the latest patches directory named remote-option.diff that
implements a means of passing options to the remote rsync in a simple manner.
This enables the ability to use "rsync -x --remote-option=--no-x" to
have
--one-file-system affect only the local side, and use "rsync
--remote-option=-x" to have the option affect only the remote side. The
new
option also helps out with --fake-super, --log-file, and other similar options
(as Matt noted).
Let me know what you think.
You can find the patch here:
http://rsync.samba.org/ftp/rsync/dev/patches/remote-option.diff
And it applies to the latest nightly tar-file or git checkout.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Maybe Matching Threads
- Feature Request: Options to limit --one-file-system at the source or destination.
- DO NOT REPLY [Bug 6240] New: rsync 3.0.x -x/--one-file-system regression?
- DO NOT REPLY [Bug 6915] New: Reject passing an argument to an option that doesn't take one
- DO NOT REPLY [Bug 5665] New: need option to hard link from source tree to dest tree
- DO NOT REPLY [Bug 5455] New: destination files with resource forks now have current mtime