Philippe Naudin wrote: > This is not the only difference between rsync-2.x and 3.x. > > We are doing > rsync -azX --delete-after etc... > and it fails with rsync-3. > > On the server (still running rsync-2), /var/log/secure shows the > difference (sorry for the long lines). >> From a rsync-2 client, we receive : > Sep 7 12:35:01 lasbHOME scponly[6166]: running: /usr/bin/rsync --server -lXogDtprz --delete --delete-after etc... >> From a rsync-3 client, it turns to : > Sep 7 20:35:01 lasbHOME scponly[12764]: option 'e' or a related long option is not permitted for use with /usr/bin/rsync (arg was .is) > Sep 7 20:35:01 lasbHOME scponly[12764]: requested command (/usr/bin/rsync --server -logDtpXrze.is --delete-after etc...) tried to use disallowed argument google says this seems to be a problem with scponly, not rsync per se. HTH