On Wed, Aug 27, 2003 at 10:32:57AM +0530, Anand Raman wrote:
> Thanks jw
>
> Your suggestion of removing -e from the rsync options seems to have
> fixed the problem. We have been able to synchornize large number of
> files between the 3 environments with no weird protocol
> incompatibilities or freezes..
Glad to hear it. If only you could get that kind of support
from the proprietary so-called enterprise software products.
> Do you think it is better idea use ssh instead of rsh to overcome the
> blocking/non-blocking io incompatibility.
My understanding is that rsync functions somewhat better
with a non-blocking connection. Rsh clearly does not
function well non-blocking.
There do seem to be more problems with rsh than openssh. This
is may be because ssh is used even more extensively as a
pipe between systems and because it has the advantage of
later projects. I can, however, say that the ssh/openssh
supplied by Sun seems to have problems. It is best to build
openssh from source.
> The environments are internal environments not visible to the outside
> world and hence could do without ssh
If rsh is working for you, great! Use what works. As long
as security is not an issue, fine. Of course i don't
trust rsh on a network where i cannot trust every machine
and person with access.
For disaster recovery rsh does have the advantage of
lowering the prerequisites. That can be worth a lot.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: [EMAIL PROTECTED]
Remember Cernan and Schmitt
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
