From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16648 invoked by alias); 30 Mar 2011 14:37:35 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 15906 Received: (qmail 1138 invoked from network); 30 Mar 2011 14:37:32 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <110330073721.ZM618@torch.brasslantern.com> Date: Wed, 30 Mar 2011 07:37:21 -0700 In-reply-to: Comments: In reply to Simon Mages "file transfer with zsh" (Mar 30, 2:09pm) References: X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Simon Mages , zsh-users@zsh.org Subject: Re: file transfer with zsh MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Mar 30, 2:09pm, Simon Mages wrote: } } I have to transfer archives from many Solaris 10 Machines to one of them. I } can't use FTP, NFS or Netcat because they are not installed or blocked and } SCP (SFTP) is to slow. If SFTP is too slow, you're not likely to write a shell script that outperforms it enough to make any useful difference. Have you checked whether rsync will work? That'd be your most efficient option. What is it you were hoping to do? Set up your own service listening on a port on one machine and connect to it from another? That's done with the tcp_point and tcp_shoot commands; run tcp_point on the destination machine and then tcp_shoot on the source machine. There's an example of this in the documentation. "sum" or "md5sum" the files on both sides after transfer to make sure nothing was lost or corrupted. However, if you can set up tcp_point on an open port on the target machine, you ought to be able to set up an rsync daemon instead, and that'll be much more reliable and probably a lot faster. Failing that, I'd recommend instead that you create an account on one of the cloud-based file-sharing services like dropbox.com or the recently- announced Amazon cloud drive or even Amazon S3. Push the archives there and then pull them down to the target. Yes, this theoretically takes twice as long as direct transfer but should be reliable and possibly automatic (hmm, I don't know if e.g. dropbox has a Solaris client).