On Sun 03 Aug 2008, Oswald Buddenhagen wrote:
>
> if i run
> rsync rsync.kernel.org::pub/linux/kernel/v2.6/ChangeLog-2.6.26.1
> ./linux-ChangeLog-2.6.26.1
> i get this:
> [MOTD snipped]
> rsync: on remote machine: -: unknown option
> rsync error: requested action not supported (code 4) at clientserver.c(685)
> [sender=2.6.9]
> rsync: read error: Connection reset by peer (104)
> rsync error: error in rsync protocol data stream (code 12) at io.c(794)
> [receiver=3.0.3]
>
> now, if i add just one -v switch to the command line, it magically works.
I first thought that this might be the -e option issue:
- If the user specifies --protocol=29, rsync will avoid sending an -e
option to the server (which is only useful for protocols 30 and above
anyway). This gives the user an easy way to talk to a restricted server
that has overly restrictive option-checking.
but you're using 3.0.3-2 and that has a patch for that, so it must be
something else. However, the rsync.kernel.org I see from here is a
3.0.0 or higher version, as it announces it's talking protocol version
30, and it does your example transfer just fine...
If you can find another way of reproducing this, then we can
investigate, but I wonder if it might not be dependent on the way that
rsync was configured...
Paul Slootman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
