<div class="gmail_quote">On Sat, Mar 27, 2010 at 7:23 AM, Gerald Holl <span dir="ltr"><<a href="mailto:gerald@holl.co.at">gerald@holl.co.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">that was the final hint! I specified e.iL in command="..." in</div>
ssh/authorized_keys and now incremental recursion works!<br></blockquote></div><br clear="all">Rsync depends on being able to communicate what is happening to the remote side via options. If something is mangling the options, any number of things can break, sometimes in spectacular ways. So, unless you always run the exact same rsync command into the server, you should figure out some way for rsync to communicate what it is doing. One way is to force a single-use-daemon rsync (force the command "rsync --server --daemon ."), and using a combined ssh+daemon rsync request (after you setup a local rsyncd.conf file for the user).<div>
<br>..wayne..<br>
</div>