samba-bugs | 23 Oct 19:40 2014
Picon

[Bug 10893] New: Allow option to sync symlinks last (or delayed)

https://bugzilla.samba.org/show_bug.cgi?id=10893

            Bug ID: 10893
           Summary: Allow option to sync symlinks last (or delayed)
           Product: rsync
           Version: 3.1.1
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: moffatjd <at> gmail.com
        QA Contact: rsync-qa <at> samba.org

Presently rsync will create symlinks first (on the receiver side) and then it
will sync the content that is potentially being linked. This can cause race
conditions on the receiver side.

For example, given the small hierarchy already existing on the receiver side:

/foo -> foo_1.0
/foo_1.0

And then assume we have an updated hierarchy on the sender side:

/foo -> foo_2.0
/foo_1.0
/foo_2.0
(Continue reading)

samba-bugs | 20 Oct 22:12 2014
Picon

[Bug 10857] weirdly named files fail remotely

https://bugzilla.samba.org/show_bug.cgi?id=10857

--- Comment #7 from Wayne Davison <wayned <at> samba.org> ---
Those are both the same on the rsync side of the pipe.  Use: rsync -aR {} dest/
(where dest is a directory path or a host:directory combo for the root dir of
the destination hierarchy).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

samba-bugs | 19 Oct 11:25 2014
Picon

[Bug 10857] weirdly named files fail remotely

https://bugzilla.samba.org/show_bug.cgi?id=10857

--- Comment #6 from samba.org <at> tange.dk <samba.org <at> tange.dk> ---
> As for this:
>
>    find . -type f -print0 | parallel -0 rsync {} remote:backup/{}

Is there also a better way for:

    find . -type f -size +1000 -print0 | parallel -0 rsync {} remote:backup/{}

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

samba-bugs | 18 Oct 19:56 2014
Picon

[Bug 10857] weirdly named files fail remotely

https://bugzilla.samba.org/show_bug.cgi?id=10857

--- Comment #5 from Wayne Davison <wayned <at> samba.org> ---
If rsync begins quoting remote args, it would make assumptions about what needs
to be quoted and its rules for quoting things.  There is also a historical use
of arg-splitting that was primarily used on the source side, e.g. "rsync -a
host:"file1 file2" /dest/" that has been replaced by "rsync -a
host:{file1,file2} /dest/" (which results in 2 host:file* args).

If we assume that enough time has passed to discard the backward compatibility
issue, the more proper solution is to avoid sending such args to the remote
shell in the first place, and that is what --protect-args does.  So, the really
we should just make --protect-args the default (forcing users interacting with
older rsync versions to specify --no-s when they get an option error).  This is
certainly what I have done for years now, and is probably what I should go
ahead and make the default in an upcoming configure.

Folks can also affect their own rsync use by putting "export
RSYNC_PROTECT_ARGS=1" in their environment, perhaps even in an
/etc/profile.d/rsync.sh file.  We can at the very least make this clearer in
the manpage.

As for this:

    find . -type f -print0 | parallel -0 rsync {} remote:backup/{}

The better way to do that is to specify -R (and -a) and omit the second {}
(especially since the original way can fail if the destination dir doesn't
exist).  FYI.

(Continue reading)

samba-bugs | 13 Oct 00:44 2014
Picon

[Bug 10857] weirdly named files fail remotely

https://bugzilla.samba.org/show_bug.cgi?id=10857

--- Comment #4 from samba.org <at> tange.dk <samba.org <at> tange.dk> ---
Can we start by agreeing that rsync _could_ be aware that it is starting a
remote shell and thus _could_ quote anything that needed quoting?

Currently it clearly does not quote and puts that responsibility on the user.

My question is: Why put that responsibility on the user? Why not help the user?
Rsync knows in advance that files with weird characters will cause problems, so
why not help the user by quoting them correctly?

In other words: What situations will break if --protect-args becomes the
default?

Is rsync following the principle of least surprise by not having --protect-args
be default, and thus requiring users to write the remote file differently than
the local file?

I would say rsync is breaking that principle: I as a user assume that I can
express the remote file name the same way as the local. There might be good
reasons for breaking the POLS, but so far I have not heard any. So let me ask
again: Are there any?

I can see how the current behaviour can be abused by a malicious user if the
user knows that 'root' copies files like this:

    find . -type f -print0 | parallel -0 rsync {} remote:backup/{}

Just:
(Continue reading)

samba-bugs | 12 Oct 21:20 2014
Picon

[Bug 10857] weirdly named files fail remotely

https://bugzilla.samba.org/show_bug.cgi?id=10857

--- Comment #3 from Kevin Korb <rsync <at> sanitarium.net> ---
This isn't an rsync problem this is the way the shell works.  When you run
rsync over ssh as you are doing there rsync is running 'ssh remotehost rsync
[options] path'.  There is a shell between the sshd process and the remote
rsync process.  Therefore you have 2 layers of shell involved and have to deal
with both of them rather than just 1.

You would run into the same problem any time you double stack a shell:
echo "doesn't work"
vs
sh -c 'echo "doesn't work"'

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

samba-bugs | 12 Oct 17:07 2014
Picon

[Bug 10857] weirdly named files fail remotely

https://bugzilla.samba.org/show_bug.cgi?id=10857

--- Comment #2 from samba.org <at> tange.dk <samba.org <at> tange.dk> ---
I understand what is happening and I know the workarounds for the bug - that is
not the issue.

Why is it that rsync prefers having a syntax, where if I transfer the file
locally I need to write something, but if I transfer the file remotely I need
to write something completely different?

Can you elaborate what situations this behaviour is beneficial and what would
break if this was changed to being able to write the same name whether the
transfer was local or remote?

I discovered the problem when writing a script, and I find it surprising that
you prefer, that I deal with the quoting in my script if and only if the
transfer is remote; instead of having rsync Do The Right Thing(TM) by default.

There may be situations where the current behaviour is preferable that I am
unaware of, and it would be great if you could describe those.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

(Continue reading)

samba-bugs | 10 Oct 23:08 2014
Picon

[Bug 10857] weirdly named files fail remotely

https://bugzilla.samba.org/show_bug.cgi?id=10857

Wayne Davison <wayned <at> samba.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|NEW                         |RESOLVED

--- Comment #1 from Wayne Davison <wayned <at> samba.org> ---
Your problem is that you tried to specify a weird filename as a part of a
remote filename without escaping the characters from the remote shell
translating them.  You can use --protect-args to avoid the issue (which I have
set as my default due to my using "./configure --with-protected-args" whenever
I compile rsync).  You would also not have run into an issue if you had just
specified a destination path and let rsync send the filename as a part of the
file list.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Romel Khan | 9 Oct 04:15 2014
Picon
Picon

rsync filter parameter in rsyncd.conf file

I would like to push a file, /home/cfg/temp, from client to a server with rsync in daemon mode to /n2p/cfg directory. How should I set the filter/include/exclude parameters on the server side rsyncd.conf file so server will disallow receiving any files from the client other than /home/cfg/temp?

--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Wieland Hoffmann | 4 Oct 10:07 2014
Picon

[PATCH] rsync.yo: Add a missing closing parentheses

---
 rsync.yo | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rsync.yo b/rsync.yo
index 87028ca..eef47e9 100644
--- a/rsync.yo
+++ b/rsync.yo
 <at>  <at>  -2449,7 +2449,7  <at>  <at>  transfer that may be interrupted.

 There is also a bf(--info=progress2) option that outputs statistics based
 on the whole transfer, rather than individual files.  Use this flag without
-outputting a filename (e.g. avoid bf(-v) or specify bf(--info=name0) if you
+outputting a filename (e.g. avoid bf(-v) or specify bf(--info=name0)) if you
 want to see how the transfer is doing without scrolling the screen with a
 lot of names.  (You don't need to specify the bf(--progress) option in
 order to use bf(--info=progress2).)
-- 
2.1.2

--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Dave Gradwell | 3 Oct 19:24 2014
Picon

Mac Backup App

Hello,

I am writing a backup application for Apple Macs which uses rsync at its core
and I'd greatly appreciate any testing/feedback.

It's detailed here:
http://bonhardcomputing.com/backaroo/

you can download it here:
http://bonhardcomputing.com/downloads/

and send any feedback to:   info  at  bonhardcomputing.com

(Please excuse the misuse of the rsync mailing list.)

Regards,

Dave.
--

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Gmane