Ahhh yes.. I completely forgot about this. I've messed around with rsync long ago. It worked reliably and supported ssh.
Shouldn't be all that tough to install rsync on the remote system if they don't already have it. I'd recommend it. Frank Cameron Simpson wrote: >>On 10:33 04 Mar 2002, Frank Carreiro <[EMAIL PROTECTED]> wrote: >>| >>>>>ncftp IS ftp. Comparing it to scp doesn't make sense. >>| >>>>>Why not use sftp instead? You are not required to input the path and >>| >>>>>it's very much like what you are doing now. >>| >>> >>| >>>Except that, as far as I can tell, sftp doesn't do directories or >>| >>>wildcards; only individual files ... nothing in the man page, at >>| >>>least. >>| >> >>| Does ncftp do directories? I was unaware of any ftp product with this >>| ability. If you could I would simply tar/gzip it then sftp the file(s) >>| across. >> >>For directories I tend to use rsync with ssh as the transport. Just >>set $RSYNC_RSH to "ssh" and go: > Good plan, but one that depends on the existence of rsync on the remote ... - -d - -- David Talkington PGP key: http://www.prairienet.org/~dtalk/0xCA4C11AD.pgp _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
